From: Vladimir Prus <vladimir@codesourcery.com>
To: Nick Roberts <nickrob@snap.net.nz>,
Marty Leisner <leisner@rochester.rr.com>,
gdb@sourceware.org
Subject: Re: breaking on open(2) on linux
Date: Tue, 15 Apr 2008 10:27:00 -0000 [thread overview]
Message-ID: <200804151211.33371.vladimir@codesourcery.com> (raw)
In-Reply-To: <20080413213803.GA12877@caradoc.them.org>
On Monday 14 April 2008 01:38:03 Daniel Jacobowitz wrote:
> On Sun, Apr 13, 2008 at 08:55:55PM +1200, Nick Roberts wrote:
> > Do you mean multiple breakpoint locations? With 6.8.50.20080411-cvs I just get
> > one address: the one in libpthread.so.
>
> Indeed it does not seem to work:
>
> #12 0x0000000000000000 in ?? ()
> (gdb) i func ^open$
> All functions matching regular expression "^open$":
>
> Non-debugging symbols:
> 0x00002aaaaaabea70 open
> 0x00002aaaadc21a50 open
> 0x00002aaaadc21a50 open
> (gdb) b open
> Breakpoint 2 at 0x2aaaadc21a50
> (gdb) i breakpoints
> Num Type Disp Enb Address What
> 1 breakpoint del y <PENDING> main
> 2 breakpoint keep y 0x00002aaaadc21a50 <open>
>
> Vladimir, can you see any reason this wouldn't work with multiple
> minimal symbols? Maybe the multiple location support is entirely
> in the partial/full symbol and line number based breakpoint support?
The multiple location support only works if there line number information
for all locations.
We discussed this (maybe internally) -- the really right solution would
require modifying the symbol table interfacecs to allow to return several
symbols for a single name. It's hard.
- Volodya
next prev parent reply other threads:[~2008-04-15 8:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-12 23:12 Marty Leisner
2008-04-13 4:18 ` Kip Macy
2008-04-13 6:13 ` Nick Roberts
2008-04-13 6:41 ` Daniel Jacobowitz
2008-04-13 21:38 ` Marty Leisner
2008-04-13 21:41 ` Nick Roberts
2008-04-13 22:05 ` Daniel Jacobowitz
2008-04-15 10:27 ` Vladimir Prus [this message]
2008-04-16 0:47 ` Eli Zaretskii
2008-04-16 15:29 ` Vladimir Prus
2008-04-20 14:32 ` Eli Zaretskii
2008-04-21 12:57 ` Vladimir Prus
2008-04-13 8:56 ` Marty Leisner
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=200804151211.33371.vladimir@codesourcery.com \
--to=vladimir@codesourcery.com \
--cc=gdb@sourceware.org \
--cc=leisner@rochester.rr.com \
--cc=nickrob@snap.net.nz \
/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