From: Mark Kettenis <kettenis@chello.nl>
To: mludvig@suse.cz
Cc: ac131313@redhat.com, gdb@sources.redhat.com
Subject: Re: Call i386_frame_p() only for 32bits
Date: Fri, 21 Mar 2003 11:05:00 -0000 [thread overview]
Message-ID: <200303211105.h2LB5Lrc000364@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <3E7AE4A3.60601@suse.cz> (message from Michal Ludvig on Fri, 21 Mar 2003 11:08:35 +0100)
Date: Fri, 21 Mar 2003 11:08:35 +0100
From: Michal Ludvig <mludvig@suse.cz>
Hi all,
I have this problem with i386newframe-branch on x86-64:
In i386-tdep.c:i386_gdbarch_init() there is always called the line
frame_unwind_append_predicate (gdbarch, i386_frame_p);
regardless if the inferior is 32b or 64b (of course, it isn't yet known
at this time). This is obviously wrong, because what i386_frame_p()
gives out doesn't make sense for 64b processes.
How can I achieve that i386_frame_p() is registered only for 32b
processes and x86_64_frame_p() only for 64b ones?
The code is laid out in such a way that if you call
frame_unwind_append_preducte (gdbarch, x86_64_frame_p)
in your x86_64-specific init_abi functions, and make sure you never
return NULL, GDB should never use the 32-bit i386 unwinder.
Mark
next prev parent reply other threads:[~2003-03-21 11:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-21 10:08 Michal Ludvig
2003-03-21 11:05 ` Mark Kettenis [this message]
2003-03-21 11:35 ` Michal Ludvig
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=200303211105.h2LB5Lrc000364@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=ac131313@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=mludvig@suse.cz \
/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