From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Joel Brobecker <brobecker@adacore.com>, Hui Zhu <teawater@gmail.com>
Subject: Re: [RFA] Fix "Segmentation fault" when "gdb -v"
Date: Thu, 04 Mar 2010 14:59:00 -0000 [thread overview]
Message-ID: <201003041459.49275.pedro@codesourcery.com> (raw)
In-Reply-To: <201003041402.07512.pedro@codesourcery.com>
On Thursday 04 March 2010 14:02:07, Pedro Alves wrote:
> I agree, and turns out this is what's already happening, albeit in
> a "works almost by accident" way. I think this patch below wouldn't
> be that bad afterall. It does fix the problem.
I went ahead and applied this. Thanks.
> 2010-03-04 Pedro Alves <pedro@codesourcery.com>
>
> * utils.c (fputs_maybe_filtered): Check if there's already a top
> level interpreter before dereferencing it. If there isn't one,
> don't paginate either.
--
Pedro Alves
next prev parent reply other threads:[~2010-03-04 14:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 6:50 Hui Zhu
2010-03-04 7:26 ` Joel Brobecker
2010-03-04 8:06 ` Hui Zhu
2010-03-04 13:45 ` Daniel Jacobowitz
2010-03-04 14:02 ` Pedro Alves
2010-03-04 14:59 ` Pedro Alves [this message]
2010-03-05 4:59 ` Joel Brobecker
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=201003041459.49275.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=teawater@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