From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [gdbserver, doc] add command line option to force core dump on fatal errors
Date: Thu, 15 Sep 2011 08:18:00 -0000 [thread overview]
Message-ID: <20110915063020.GA18166@host1.jankratochvil.net> (raw)
In-Reply-To: <201109141639.07804.pedro@codesourcery.com>
On Wed, 14 Sep 2011 17:39:07 +0200, Pedro Alves wrote:
> gdbserver does `exit(1)' on fatal errors, instead of aborting,
> because we don't normally want embedded/deployed targets to end
> up filled with core files if gdbserver happens to trip on some bug.
>
> However, when running the testsuite (and other situations) against
> gdbserver, it's quite useful to have it dump core.
I would make it more simple to abort always, there is already `ulimit -c' to
control whether one wants a core file or not.
> (yes, I know we should try to increase the core soft limit like
> gdb does before calling abort. I'm leaving that to a follow
> up, possibly moving dump_core to common/).
The soft limit bump could be rather controlled by `--internal-error-corefile'.
gdbserver is different from gdb in that it is not interactive.
Thanks,
Jan
prev parent reply other threads:[~2011-09-15 6:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-14 15:45 Pedro Alves
2011-09-14 16:48 ` Eli Zaretskii
2011-09-15 8:18 ` 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=20110915063020.GA18166@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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