Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Simon Marchi <simark@simark.ca>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Also recognize __sighndlr on Solaris/x86
Date: Sun, 23 Sep 2018 18:12:00 -0000	[thread overview]
Message-ID: <yddk1nculqy.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <ca3fb627-961e-d072-196c-55d21e1e4b3b@simark.ca> (Simon Marchi's	message of "Sun, 23 Sep 2018 12:03:54 -0400")

Hi Simon,

> I noticed this had not been replied to, this LGTM.  I don't know much about
> Solaris, but I trust that you know what you are talking about :) and this
> looks pretty straightforward.

just a bit ;-)  I recognized that __sighndlr stuff from my work on the
libgcc unwinder (libgcc/config/{i386,sparc}/sol2-unwind.h) some time ago.

Thanks.
	Rainer

-- 
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University


      reply	other threads:[~2018-09-23 18:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-19 12:56 Rainer Orth
2018-09-23 16:03 ` Simon Marchi
2018-09-23 18:12   ` Rainer Orth [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=yddk1nculqy.fsf@CeBiTec.Uni-Bielefeld.DE \
    --to=ro@cebitec.uni-bielefeld.de \
    --cc=gdb-patches@sourceware.org \
    --cc=simark@simark.ca \
    /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