Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: Daniel Jacobowitz <drow@false.org>
Cc: Marty Leisner <leisner@rochester.rr.com>, gdb@sourceware.org
Subject: Re: breaking on open(2) on linux
Date: Sun, 13 Apr 2008 21:41:00 -0000	[thread overview]
Message-ID: <18433.51867.377695.993408@kahikatea.snap.net.nz> (raw)
In-Reply-To: <20080413041833.GA19526@caradoc.them.org>

 > > The breakpoint is probably being set elsewhere, e.g. open in libpthread.so
 > 
 > Nowadays (6.8) you'll get a breakpoint at every copy so it should work
 > OK.

Do you mean multiple breakpoint locations?  With 6.8.50.20080411-cvs I just get
one address: the one in libpthread.so.

My `solution' was wrong though, as the symbols for libpthread.so just get
read when a breakpoint is set on open.

For some reason in GDB 6.6, a pending breakpoint gets resolved in libc.so
while in 6.8.50.20080411-cvs it gets resolved in  libpthread.so.

-- 
Nick                                           http://www.inet.net.nz/~nickrob


  parent reply	other threads:[~2008-04-13  8:56 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 [this message]
2008-04-13 22:05       ` Daniel Jacobowitz
2008-04-15 10:27         ` Vladimir Prus
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=18433.51867.377695.993408@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=leisner@rochester.rr.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