From: Mark Kettenis <kettenis@chello.nl>
To: cagney@gnu.org
Cc: jjohnstn@redhat.com, kevinb@redhat.com,
gdb-patches@sources.redhat.com, marcel@xcllnt.net
Subject: Re: RFA: ia64 patch required after recent osabi changes
Date: Wed, 05 Nov 2003 21:43:00 -0000 [thread overview]
Message-ID: <200311052143.hA5LhB79020073@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <3FA9619F.8030803@gnu.org> (message from Andrew Cagney on Wed, 05 Nov 2003 15:46:23 -0500)
Date: Wed, 05 Nov 2003 15:46:23 -0500
From: Andrew Cagney <cagney@gnu.org>
> Patch checked in. This fixes the regression with the new osabi
> code and ia64 signal handling backtrace without having to remove
> the assertion.
Nice. So everyone's clear, the assertion is correct and needed.
The function is forcing an architecture switch so if the switch fails
(what the assertion was checking) GDB's a bit stuffed.
Great! Thanks folks, for resolving this issue.
Mark
prev parent reply other threads:[~2003-11-05 21:43 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
2003-11-05 20:34 ` J. Johnston
2003-11-05 20:46 ` Andrew Cagney
2003-11-05 21:43 ` Mark Kettenis [this message]
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=200311052143.hA5LhB79020073@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=jjohnstn@redhat.com \
--cc=kevinb@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