From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: pgilliam@us.ibm.com
Cc: gdb-patches@sourceware.org
Subject: Re: patch: signal trampoline frame cache corruption (repost?)
Date: Tue, 31 Oct 2006 23:28:00 -0000 [thread overview]
Message-ID: <200610312328.k9VNScRC012608@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <1162323227.3428.9.camel@dufur.beaverton.ibm.com> (message from PAUL GILLIAM on Tue, 31 Oct 2006 11:33:47 -0800)
> From: PAUL GILLIAM <pgilliam@us.ibm.com>
> Date: Tue, 31 Oct 2006 11:33:47 -0800
>
> This might be a repost.
>
> Attached is a patch to fix some signal trampoline frame cache corruption
> that occurs on machines that have no FPU registers. The corruption was
> reported when running gdb 6.4 on a PowerPC 440. If a backtrace command
> was run after hitting a signal trampoline frame, the frame cache would
> become corrupted and GDB would SIGSEGV.
>
> I have checked the cvs head sources, and the code has moved, but has not
> been fixed. So I updated the patch to apply to cvs head.
>
> Ok to commit? (This is almost an obvious fix, isn't it?)
Not as you've posted it, since it doesn't adhere to the GNU coding
style. But the idea seems alright to me.
Mark
next prev parent reply other threads:[~2006-10-31 23:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-31 19:41 PAUL GILLIAM
2006-10-31 23:28 ` Mark Kettenis [this message]
2006-11-03 17:58 ` PAUL GILLIAM
2006-11-10 21:22 ` Daniel Jacobowitz
2006-11-13 17:42 ` [commit] signal trampoline frame cache corruption PAUL GILLIAM
2006-11-13 17:46 ` Daniel Jacobowitz
2006-11-13 18:57 ` PAUL GILLIAM
2006-11-13 19:05 ` Daniel Jacobowitz
2006-11-14 1:50 ` PAUL GILLIAM
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=200610312328.k9VNScRC012608@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb-patches@sourceware.org \
--cc=pgilliam@us.ibm.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