Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Michael Snyder <msnyder@vmware.com>,
	       "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFA] mdebugread.c (psymtab_to_symtab_1): assert that 'fh' is not null
Date: Mon, 07 Mar 2011 17:21:00 -0000	[thread overview]
Message-ID: <20110307165301.GA25669@host1.jankratochvil.net> (raw)
In-Reply-To: <m34o7eop9i.fsf@fleche.redhat.com>

On Mon, 07 Mar 2011 17:43:05 +0100, Tom Tromey wrote:
> >>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
> 
> Jan> (*) In fact I like the crash from the Fedora point of view better as ABRT
> Jan>     (Automatic Bug Reporting Tool) will automatically report it.  In the case
> Jan>     of a failed gdb_assert the user may or may not allow the core dump and
> Jan>     therefore the crash bugreport by ABRT may be suppressed.
> Jan> 	A problem internal to GDB has been detected,
> Jan> 	further debugging may prove unreliable.
> Jan> 	Create a core file of GDB? (y or n) n
> Jan>     This is just FYI and it should not be related to FSF GDB maintenance.
> 
> Then perhaps we should disable this in Fedora, or at least mention ABRT
> in the note.

It is more complicated, it should:
without ABRT:
  create core file: n => nothing happens
  create core file: y => ulimit -c unlimited + crash
with ABRT:
  create core file: n => keep ulimit -c 0 + crash
  create core file: y => ulimit -c unlimited + crash

As ABRT always catches any crash even with ulimit -c 0 but it leaves the
regular core file at currentdir as if no ABRT was running.


Thanks,
Jan


      reply	other threads:[~2011-03-07 16:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-04 22:15 Michael Snyder
2011-03-06 16:17 ` Jan Kratochvil
2011-03-06 18:54   ` Michael Snyder
2011-03-06 19:05     ` Jan Kratochvil
2011-03-07 16:53       ` Tom Tromey
2011-03-07 17:21         ` Jan Kratochvil [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=20110307165301.GA25669@host1.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.com \
    --cc=tromey@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