From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC/ia64-linux] pb with shared libraries when attaching to process
Date: Fri, 25 Apr 2008 02:36:00 -0000 [thread overview]
Message-ID: <20080425014746.GA10244@caradoc.them.org> (raw)
In-Reply-To: <20080425012331.GP1431@adacore.com>
On Thu, Apr 24, 2008 at 06:23:31PM -0700, Joel Brobecker wrote:
> (gdb) maintenance info break
> Num Type Disp Enb Address What
> -1 shlib events keep y 0x200000000003b768 <local+168>
>
> (the slot number is encoded in the last 4 bits of the address and
> should be either 0, 1, or 2).
So what's actually at that address? Dump a couple of words... my
first guess is that it ends up being a function descriptor for
_dl_debug_state, but GDB is somehow failing to convert it back into
the breakpoint address.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-04-25 1:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-25 2:06 Joel Brobecker
2008-04-25 2:36 ` Daniel Jacobowitz [this message]
2008-04-25 14:26 ` Joel Brobecker
2008-04-25 16:15 ` Daniel Jacobowitz
2008-04-25 19:00 ` Joel Brobecker
2008-05-02 15:01 ` Daniel Jacobowitz
2008-05-07 10:12 ` Joel Brobecker
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=20080425014746.GA10244@caradoc.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@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