Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: gdb-patches@sourceware.org
Cc: Andrew Pinski <pinskia@gmail.com>
Subject: Re: [PATCH] Fix regression: cannot start with LD_PRELOAD=libSegFault.so (PR gdb/18653#c7)
Date: Fri, 05 Jan 2018 18:34:00 -0000	[thread overview]
Message-ID: <c03925f0-a156-5db9-9ff5-b4b2fe95b274@redhat.com> (raw)
In-Reply-To: <1513305092-8610-1-git-send-email-palves@redhat.com>

On 12/15/2017 02:31 AM, Pedro Alves wrote:
> At https://sourceware.org/bugzilla/show_bug.cgi?id=18653#c7, Andrew
> reports that the fix for PR gdb/18653 made GDB useless if you preload
> libSegFault.so, because GDB internal-errors on startup:
> 

...

> gdb/ChangeLog:
> yyyy-mm-dd  Pedro Alves  <palves@redhat.com>
> 
> 	* common/signals-state-save-restore.c
> 	(save_original_signals_state): New parameter 'quiet'.  Warn if we
> 	find a custom handler preinstalled, instead of internal erroring.
> 	But only warn if !quiet.
> 	* common/signals-state-save-restore.h
> 	(save_original_signals_state): New parameter 'quiet'.
> 	* main.c (captured_main_1): Move save_original_signals_state call
> 	after option handling, and pass QUIET.
> 
> gdb/gdbserver/ChangeLog:
> yyyy-mm-dd  Pedro Alves  <palves@redhat.com>
> 
> 	* server.c (captured_main): Pass quiet=false to
> 	save_original_signals_state.
> 
> gdb/testsuite/ChangeLog:
> yyyy-mm-dd  Pedro Alves  <palves@redhat.com>
> 
> 	* gdb.base/libsegfault.exp: New.

I've pushed this in, both master and 8.1 branch.

Thanks,
Pedro Alves


  reply	other threads:[~2018-01-05 18:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-15  2:31 Pedro Alves
2018-01-05 18:34 ` Pedro Alves [this message]
2018-01-05 19:07 ` Andreas Schwab
2018-01-15 22:13   ` Pedro Alves

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=c03925f0-a156-5db9-9ff5-b4b2fe95b274@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pinskia@gmail.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