From: "Sébastien Granjoux" <seb.sfo@free.fr>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb@sourceware.org
Subject: Re: Breakpoint doesn't take in account full name in gdb 6.8
Date: Fri, 25 Jul 2008 18:22:00 -0000 [thread overview]
Message-ID: <488A1432.3030305@free.fr> (raw)
In-Reply-To: <g6bplj$p3g$1@ger.gmane.org>
Hi,
Vladimir Prus a écrit :
> What functions are at the location where you've set breakpoint, and at the location
> where GDB has stopped.
I have set the breakpoint at
/home/seb/Programmation/Anjuta/anjuta/plugins/debug-manager/plugin.c:232
in a function named value_added_project_root_uri.
Gdb stops at /home/seb/Programmation/Anjuta/anjuta/plugins/tools/plugin.c
in a function named atp_plugin_class_init
> What is the output of "info break"?
Num Type Disp Enb Address What
1 breakpoint keep y <MULTIPLE> 0xb57c27dd
breakpoint already hit 1 time
1.1 y 0xb57c27dd in file_manager_activate
at plugin.c:232
1.2 y 0xb57a0350 in on_refresh_idle
at plugin.c:232
1.3 y 0xb5563c72 in atp_plugin_class_init
at plugin.c:232
It seems that gdb has put a breakpoint in every file named plugin.c. In
Anjuta most plugin have a the main file named plugin.c and are loaded
dynamically. When gdb stops all plugins have not been loaded. I have run
"info break" when all plugins have been loaded I get:
Num Type Disp Enb Address What
1 breakpoint keep y <MULTIPLE> 0xb57c17dd
breakpoint already hit 1 time
1.1 y 0xb57c17dd in file_manager_activate
at plugin.c:232
1.2 y 0xb579f350 in on_refresh_idle
at plugin.c:232
1.3 y 0xb5562c72 in atp_plugin_class_init
at plugin.c:232
1.4 y 0xb429bcfd in value_added_fm_current_file
at plugin.c:232
1.5 y 0xb1e0a733 in ipreferences_merge
at plugin.c:232
1.6 y 0xb34462c8 in ilanguage_get_from_mime_type
at plugin.c:232
1.7 y 0xb1d6fc73 in skip_iter_to_previous_line
at plugin.c:232
I would expect even more breakpoints, as I have 20 plugins loaded and
most of them have a plugin.c file.
Sébastien
prev parent reply other threads:[~2008-07-25 17:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-24 21:44 Sébastien Granjoux
2008-07-25 8:00 ` Vladimir Prus
2008-07-25 18:22 ` Sébastien Granjoux [this message]
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=488A1432.3030305@free.fr \
--to=seb.sfo@free.fr \
--cc=gdb@sourceware.org \
--cc=vladimir@codesourcery.com \
/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