public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "jan.kiszka at siemens dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug python/17837] New: python-injected silent breakpoints broken since 1a853c52 Date: Tue, 13 Jan 2015 14:43:00 -0000 [thread overview] Message-ID: <bug-17837-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=17837 Bug ID: 17837 Summary: python-injected silent breakpoints broken since 1a853c52 Product: gdb Version: HEAD Status: NEW Severity: critical Priority: P2 Component: python Assignee: unassigned at sourceware dot org Reporter: jan.kiszka at siemens dot com I've stumbled over a regression of gdb since commit 1a853c52 (make "permanent breakpoints" per location and disableable). My gdb python scripts [1] that load Linux kernel module symbols as the target loads the modules now fail. The involved command is lx-symbols [2]. It installs a silent breakpoint on a kernel function that is called when a module is loaded. Before 1a853c52, the python callback was normally invoked and the target continued to run. Since af48d08f (1a853c52 is not testable), the int3 instruction (I'm testing with x86) is left in the target, and garbage instructions are executed, causing a kernel oops. The breakpoint is apparently not properly skipped (remove, single-step, re-insert) when resuming the target on return from LoadModuleBreakpoint.stop(). I can provide more details on how to set up a reproduction case but I would only gather them when desired as that is not straightforward. [1] https://lkml.org/lkml/2014/11/20/531 [2] http://git.kiszka.org/?p=linux.git;a=blob;f=scripts/gdb/linux/symbols.py;h=bf05e451c58666add299061046bf1ceb9e82f4ef;hb=d92098e7cf60d31ccd025e56d20c23917ccd0819 -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2015-01-13 14:43 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-01-13 14:43 jan.kiszka at siemens dot com [this message] 2015-01-13 15:22 ` [Bug python/17837] " palves at redhat dot com 2015-01-13 15:41 ` jan.kiszka at siemens dot com 2015-01-13 16:07 ` palves at redhat dot com 2015-01-13 16:13 ` jan.kiszka at siemens dot com 2015-01-13 16:21 ` palves at redhat dot com 2015-01-14 7:19 ` jan.kiszka at siemens dot com 2015-01-27 22:36 ` jan.kiszka at siemens dot com 2015-01-31 14:38 ` palves at redhat dot com 2015-02-03 20:32 ` palves at redhat dot com 2015-02-04 18:17 ` jan.kiszka at siemens dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-17837-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).