public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "nickrob at snap dot net dot nz" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug mi/9583] -break-insert failed when several source files have the same name Date: Sun, 18 Jan 2009 19:13:00 -0000 [thread overview] Message-ID: <20090118191319.7879.qmail@sourceware.org> (raw) In-Reply-To: <20080720111801.9583.seb.sfo@free.fr> ------- Additional Comments From nickrob at snap dot net dot nz 2009-01-18 19:13 ------- Subject: Re: -break-insert failed when several source files have the same name > I cannot get exactly the same things so I have put a breakpoint at > plugins/debug-manager/plugin.c:232 and > plugins/language-support-cpp-java/plugin.c:1648 > > And with gdb 6.8 I get a break in plugins/language-manager/plugin.c:232 > > info break gives the following output: Several things surprise me about this output: 1) The breakpoint locations are from different files (I guess we already knew that). 2) The file plugins/language-manager/plugin.c isn't one of those files. > info break > Num Type Disp Enb Address What > 1 breakpoint keep y <MULTIPLE> 0xb5203453 ^^^^^^^^^^ 3) The hexaecimal address on the above line. This is the only line that -break-list outputs and in your earlier log it looks like: bkpt={number="2",type="breakpoint",disp="keep",enabled="y",addr="<MULTIPLE>",addr="0xb56f97dd",times="1"} and the addr field is duplicated. I don't see how this can happen in the gdb code. Are you sure this is vanilla gdb? What does "show version" say? e.g for me: GNU gdb (GDB) 6.8.50.20090116-cvs > breakpoint already hit 1 time > 1.1 y 0xb5203453 in ilanguage_get_from_mime_type at > plugin.c:232 > 1.2 y 0xb4f880ca in deactivate_plugin at plugin.c:232 > 1.3 y 0xb45f2447 in value_added_fm_current_file at > plugin.c:232 > done > > The second breakpoints have been set in several files which is wrong. The > breakpoint 1.1 is in plugins/language-manager/plugin.c:232, the breakpoint 1.2 > is in plugins/message-view/plugin.c:232, the breakpoint 1.3 is in > plugins/subversion/plugin.c:232 Is it possible to set a breakpoint after plugins/language-manager/plugin.c:232 has loaded and and do "info break" to see if this results in a normal breakpoint at the rght place? -- http://sourceware.org/bugzilla/show_bug.cgi?id=9583 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2009-01-18 19:13 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20080720111801.9583.seb.sfo@free.fr> 2009-01-18 10:18 ` nickrob at snap dot net dot nz 2009-01-18 11:15 ` seb dot sfo at free dot fr 2009-01-18 19:13 ` nickrob at snap dot net dot nz [this message] 2009-01-18 21:48 ` seb dot sfo at free dot fr 2009-01-19 20:41 ` nickrob at snap dot net dot nz 2009-01-25 18:14 ` seb dot sfo at free dot fr 2009-02-02 13:09 ` IngedevTeam dot fr at ingenico dot com 2009-02-17 14:28 ` IngedevTeam dot fr at ingenico dot com 2009-03-02 21:28 ` seb dot sfo at free dot fr 2009-03-02 21:29 ` seb dot sfo at free dot fr 2009-10-01 18:00 ` seb dot sfo at free dot fr 2009-10-01 18:00 ` seb dot sfo at free dot fr 2009-10-01 20:52 ` seb dot sfo at free dot fr 2009-10-02 20:57 ` seb dot sfo at free dot fr 2009-10-29 21:56 ` seb dot sfo at free dot fr 2009-11-09 22:03 ` cvs-commit at gcc dot gnu dot org 2009-12-03 7:04 ` vladimir at codesourcery 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=20090118191319.7879.qmail@sourceware.org \ --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).