From: Andrew Cagney <cagney@gnu.org>
To: Randolph Chung <randolph@tausq.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfa] Allow breakpoing to be added after inferior has started
Date: Tue, 25 May 2004 18:17:00 -0000 [thread overview]
Message-ID: <40B38DC8.30601@gnu.org> (raw)
In-Reply-To: <20040522023133.GG7207@tausq.org>
The shlib-call.exp test fails on hppa (also ia64) because it tries to
add a breakpoint before the inferior is started, so there's no where
to put the breakpoint. gdb can handle this case if we allow pending
breakpoints in the test.
this only works on x86 and some other architectures because they put
instructions into the plt; but some architectures put addresses in the
plt.
ok to commit?
This is sounding a lot like PIE (position independant executable): where
it isn't possible to determine a breakpoint's true (re-located) location
until after the inferior has started.
Can you describe the problem in more detail?
Andrew
2004-05-21 Randolph Chung <tausq@debian.org>
* gdb.base/shlib-call.exp: Allow breakpoint to be added after inferior
has started.
next prev parent reply other threads:[~2004-05-25 18:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-22 2:31 Randolph Chung
2004-05-25 18:17 ` Andrew Cagney [this message]
2004-05-25 18:30 ` Randolph Chung
2004-06-07 3:04 ` Randolph Chung
2004-06-07 15:20 ` Daniel Jacobowitz
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=40B38DC8.30601@gnu.org \
--to=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=randolph@tausq.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