public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "dave at treblig dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug breakpoints/15413] New: reliable seg in gdb/breakpoint.c:condition_completer Date: Sun, 28 Apr 2013 16:32:00 -0000 [thread overview] Message-ID: <bug-15413-4717@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=15413 Bug #: 15413 Summary: reliable seg in gdb/breakpoint.c:condition_completer Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: breakpoints AssignedTo: unassigned@sourceware.org ReportedBy: dave@treblig.org Classification: Unclassified Hi, There is a trivially repeatable seg in condition_completer on head; this was originally filed by Borim here; I as triaging it: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1171511 I've repeated this on CVS head; to trigger: (Original reporter) 1. Start gdb with any program you want to debug 2. set a pending breakpoint, e.g. "b nofile.cxx:54" 3. type "condition 1" + Tab This seems to come down to gdb/breakpoint.c:condition_completer which has the code: ALL_BREAKPOINTS (b) { 1016 int single = b->loc->next == NULL; struct bp_location *loc; int count = 1; for (loc = b->loc; loc; loc = loc->next) { That 'int single' line is where it segs because b->loc is NULL; I think turning it into something like int single; ... single = (b->loc)?(b->loc->next==NEXT):1 would do it, but I've not really dug into the datastructure to check what else that might do. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2013-04-28 16:32 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-04-28 16:32 dave at treblig dot org [this message] 2013-04-28 16:32 ` [Bug breakpoints/15413] " dave at treblig dot org 2013-05-06 0:12 ` sergiodj at redhat dot com 2013-05-06 0:14 ` sergiodj at redhat dot com 2013-05-07 17:04 ` cvs-commit at gcc dot gnu.org 2013-05-07 17:04 ` cvs-commit at gcc dot gnu.org 2013-05-07 17:08 ` sergiodj at redhat 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-15413-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).