From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Do not disappoint on "Create a core file of GDB?"
Date: Tue, 12 Jan 2010 16:58:00 -0000 [thread overview]
Message-ID: <m31vhvnttj.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20100111160241.GA12356@host0.dyn.jankratochvil.net> (Jan Kratochvil's message of "Mon, 11 Jan 2010 17:02:41 +0100")
Jan> this is a FAQ, GDB asks "Create a core file of GDB?", user types
Jan> "y" but a core file is never created.
[...]
Jan> Even in the case of "maint set internal-error corefile yes" it had
Jan> to be set explicitly by the user as the default is "ask", therefore
Jan> it should override the soft core limit.
This seems reasonable.
Jan> 2010-01-11 Jan Kratochvil <jan.kratochvil@redhat.com>
Jan> * configure.ac (AC_CHECK_FUNCS): Check for setrlimit and getrlimit.
Jan> * configure: Regenerate.
Jan> * config.in: Regenerate.
Jan> * utils.c: Include sys/resource.h.
Jan> (dump_core, can_dump_core): New.
Jan> (internal_vproblem): Update the comment. Check can_dump_core while
Jan> setting dump_core_p. Replace two abort calls by dump_core calls.
Looks good to me.
Ok.
Tom
next prev parent reply other threads:[~2010-01-12 16:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-11 16:03 Jan Kratochvil
2010-01-11 16:06 ` Tristan Gingold
2010-01-11 16:18 ` Jan Kratochvil
2010-01-11 19:15 ` Eli Zaretskii
2010-01-12 8:44 ` Tristan Gingold
2010-01-12 19:37 ` Eli Zaretskii
2010-01-15 0:28 ` Jan Kratochvil
2010-01-15 8:24 ` Eli Zaretskii
2010-01-12 16:58 ` Tom Tromey [this message]
2010-01-15 0:35 ` Jan Kratochvil
2010-01-30 13:05 ` Mark Kettenis
2010-01-30 14:47 ` Jan Kratochvil
2010-01-31 14:13 ` Mark Kettenis
2010-03-31 13:38 ` Pierre Muller
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=m31vhvnttj.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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