public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "seb dot sfo at free dot fr" <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 11:15:00 -0000 [thread overview]
Message-ID: <20090118111523.26041.qmail@sourceware.org> (raw)
In-Reply-To: <20080720111801.9583.seb.sfo@free.fr>
------- Additional Comments From seb dot sfo at free dot fr 2009-01-18 11:15 -------
(In reply to comment #1)
> The output to -break-list is known to be broken for multiple breakpoints.
> What do you get if you type "info break" (assuming Anjuta has a console)
> before/after hitting the breakpoint?
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:
info break
Num Type Disp Enb Address What
1 breakpoint keep y <MULTIPLE> 0xb5203453
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
--
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 11:15 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 [this message]
2009-01-18 19:13 ` nickrob at snap dot net dot nz
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=20090118111523.26041.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: link
Be 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).