From: Richard Earnshaw <rearnsha@arm.com>
To: gdb@sources.redhat.com
Cc: Richard.Earnshaw@arm.com
Subject: multi-arch and CALL_DUMMY_BREAKPOINT_OFFSET
Date: Fri, 08 Feb 2002 03:35:00 -0000 [thread overview]
Message-ID: <200202081134.LAA07778@cam-mail2.cambridge.arm.com> (raw)
I guess I'm going to find several things like this...
Well it appears that in a multi-arch gdb (even at level 1),
CALL_DUMMY_BREAKPOINT_OFFSET can only be a constant for any particular
architecture. This is a problem, because on the ARM it is currently a
function that returns one of two values depending on whether the
call-dummy stub has to be ARM code or Thumb code. Note that both types of
code can exist within a single application and it is not always safe to
assume that every function is interworking safe.
I guess I could re-write the whole of the call-dummy stuff so that
appropriate breakpoints are built in, but that is certainly going to be
non-trivial.
Any suggestions? Can I diddle with the gdbarch setting dynamically -- eg
by calling gdbarch_set_call_dummy_breakpoint_offset() from within
arm_fix_call_dummy()? It's quite gross, but it might work.
Long term it would probably be better to rewrite the call-dummy handling
to remove the covert variable that is used to communicate between the
various call-dummy stubs, but I'd rather not do that now.
R.
next reply other threads:[~2002-02-08 11:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-08 3:35 Richard Earnshaw [this message]
2002-02-10 12:09 ` Andrew Cagney
2002-02-12 6:28 ` Richard Earnshaw
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=200202081134.LAA07778@cam-mail2.cambridge.arm.com \
--to=rearnsha@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gdb@sources.redhat.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