Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: gdb-patches@sourceware.org,
	Thomas Schwinge <thomas@codesourcery.com>,
	thomas@schwinge.name, bug-hurd@gnu.org
Subject: Re: [PATCH] hurd: unwinding support over signal trampolines
Date: Sat, 30 May 2020 11:07:20 -0400	[thread overview]
Message-ID: <ab01825a-f3f2-e3c5-1b14-7a1022b980e0@simark.ca> (raw)
In-Reply-To: <20200529230049.jmsn5nincf2453jy@function>

On 2020-05-29 7:00 p.m., Samuel Thibault wrote:
> gdb/ChangeLog:
> 
> 2020-05-29  Samuel Thibault  <samuel.thibault@ens-lyon.org>
> 
> 	* i386-gnu-tdep.c: Include "gdbcore.h"
> 	(gnu_sigtramp_code, i386_gnu_sc_reg_offset): New arrays.
>         (GNU_SIGTRAMP_LEN, GNU_SIGTRAMP_TAIL,
>         I386_GNU_SIGCONTEXT_THREAD_STATE_OFFSET): New macros
>         (i386_gnu_sigtramp_start, i386_gnu_sigtramp_p,
>         i386_gnu_sigcontext_addr): New functions
>         (i386gnu_init_abi): Register i386_gnu_sigtramp_p,
>         i386_gnu_sigcontext_addr, and i386_gnu_sc_reg_offset in the gdbarch
>         tdep.

Please add a commit message.  It should at least explain why this change is needed / desirable
(what case isn't working, what functionality is missing) and what it does to address that (not
in terms of which functions are added / removed, but how the GDB behavior changes as a
consequence of that change).  If the "how" is complex, it's always good to include some notes
about that to help those who aren't experts of the system you work on.

Simon


      reply	other threads:[~2020-05-30 15:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-29 23:00 Samuel Thibault
2020-05-30 15:07 ` Simon Marchi [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=ab01825a-f3f2-e3c5-1b14-7a1022b980e0@simark.ca \
    --to=simark@simark.ca \
    --cc=bug-hurd@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=thomas@codesourcery.com \
    --cc=thomas@schwinge.name \
    /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