Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "J. Johnston" <jjohnstn@redhat.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: change to ia64-linux-tdep.c
Date: Wed, 15 Oct 2003 22:58:00 -0000	[thread overview]
Message-ID: <3F8DD0FF.1020500@redhat.com> (raw)
In-Reply-To: <1031015223519.ZM22998@localhost.localdomain>

Kevin Buettner wrote:
> On Oct 15,  6:03pm, J. Johnston wrote:
> 
> 
>>The following changes the code in ia64_linux_sigcontext_register_address to use 
>>the fact that the sigframe has the address of the sigcontext area stored at 
>>offset 16 from the stack pointer.  This change avoids using a magic constant to 
>>find the start of the sigcontext area which may change in various kernel 
>>versions as fields are added or subtracted to the sigframe.
>>
>>Code has been tested with signal handling test cases.
>>
>>The following is an excerpt of the linux kernel sigframe.h code:
>>
>>struct sigframe {
>>         /*
>>          * Place signal handler args where user-level unwinder can find them 
>>easily.
>>          * DO NOT MOVE THESE.  They are part of the IA-64 Linux ABI and there 
>>is         * user-level code that depends on their presence!
>>          */
>>         unsigned long arg0;             /* signum */
>>         unsigned long arg1;             /* siginfo pointer */
>>         unsigned long arg2;             /* sigcontext pointer */
>>         /*
>>          * End of architected state.
>>          */
>>
>>Ok to Commit?
> 
> 
> Yes.  Definitely!
> 
> Thanks for doing this.
> 
> Kevin
> 

Patch checked into mainline.  Should patch be checked into gdb 6.0?

-- Jeff J.


  reply	other threads:[~2003-10-15 22:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-15 22:03 J. Johnston
2003-10-15 22:35 ` Kevin Buettner
2003-10-15 22:58   ` J. Johnston [this message]
2003-10-16  0:43     ` Kevin Buettner

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=3F8DD0FF.1020500@redhat.com \
    --to=jjohnstn@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kevinb@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