From: Kevin Buettner <kevinb@redhat.com>
To: "J. Johnston" <jjohnstn@redhat.com>,
gdb-patches@sources.redhat.com, kevinb@redhat.com
Cc: marcel@xcllnt.net
Subject: Re: RFA: ia64 patch required after recent osabi changes
Date: Wed, 05 Nov 2003 02:20:00 -0000 [thread overview]
Message-ID: <1031105022032.ZM25505@localhost.localdomain> (raw)
In-Reply-To: "J. Johnston" <jjohnstn@redhat.com> "RFA: ia64 patch required after recent osabi changes" (Nov 4, 7:04pm)
On Nov 4, 7:04pm, J. Johnston wrote:
> The latest changes by Mark K. have caused regressions in the ia64 signal handler
> back-tracing. What happens is that the ia64_gdbarch_init function is called
> without a bfd to calculate the os_ident field. The os_ident field is later used
> to set up the gdbarch_tdep structure which contains the sigcontext register
> address function address. We end up with an os_ident of -1 and don't set up the
> sigcontext register address function pointing to the ia64-linux-tdep.c function.
> This kills backtracing across signal handlers because we can't figure out the
> previous ip value without fishing it out of the sigcontext area.
>
> After discussing this with Andrew, it appears the ia64 code is a bit old. The
> info.osabi field is set properly so we don't have to calculate the os_ident.
> This patch removes the gdbarch_tdep os_ident field and uses instead the
> info.osabi field in ia64_gdbarch_init. It also copies code from i386 which
> looks for a gdbarch candidate. This code is much more efficient than the old code.
>
> With this patch, the ia64 signal backtracing works again and there are no
> regressions in the testsuite.
>
> Ok to commit?
>
> -- Jeff J.
>
> 2003-11-04 Jeff Johnston <jjohnstn@redhat.com>
>
> * ia64-tdep.c (struct gdbarch_tdep): Remove os_ident field.
> (ia64_gdbarch_init): Don't bother calculating the os. Instead use the
> gdbarch_info struct and look at the osabi field. Also use
> gdbarch_list_lookup_by_info() to look for a candidate gdbarch.
Approved. (But watch the line lengths on your ChangeLog entry when you
check it in...)
Thanks,
Kevin
next prev parent reply other threads:[~2003-11-05 2:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-05 0:04 J. Johnston
2003-11-05 2:20 ` Kevin Buettner [this message]
2003-11-05 20:34 ` J. Johnston
2003-11-05 20:46 ` Andrew Cagney
2003-11-05 21:43 ` Mark Kettenis
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=1031105022032.ZM25505@localhost.localdomain \
--to=kevinb@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jjohnstn@redhat.com \
--cc=marcel@xcllnt.net \
/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