public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@physics.uc.edu> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: other/10628: core file not generated Date: Tue, 06 May 2003 15:06:00 -0000 [thread overview] Message-ID: <20030506150600.13276.qmail@sources.redhat.com> (raw) The following reply was made to PR other/10628; it has been noted by GNATS. From: Andrew Pinski <pinskia@physics.uc.edu> To: Wolfgang Bangerth <bangerth@ices.utexas.edu> Cc: Andrew Pinski <pinskia@physics.uc.edu>, gcc-bugs@gcc.gnu.org, <khan_sanjay@operamail.com>, <gcc-gnats@gcc.gnu.org> Subject: Re: other/10628: core file not generated Date: Tue, 6 May 2003 10:59:01 -0400 yep. Here is the changelog for the patch that added -dH: 2003-02-11 Geoffrey Keating <geoffk@apple.com> * diagnostic.c (real_abort): New. (diagnostic_report_diagnostic): Call real_abort on error. * diagnostic.h (diagnostic_abort_on_error): New. (struct diagnostic_context): Add abort_on_error field. * toplev.c (setup_core_dumping): New. (decode_d_option): Handle 'H' case. * doc/invoke.texi (Debugging Options): Document -dH. Thanks, Andrew Pinski On Tuesday, May 6, 2003, at 10:22 US/Eastern, Wolfgang Bangerth wrote: > >> 3.4 has an option -dH. > > Does that mean that the PR is thus resolved and should be closed? > > Thanks > W. > > ----------------------------------------------------------------------- > -- > Wolfgang Bangerth email: > bangerth@ices.utexas.edu > www: > http://www.ices.utexas.edu/~bangerth/ > > > >
next reply other threads:[~2003-05-06 15:06 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-06 15:06 Andrew Pinski [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-06 15:03 bangerth 2003-05-06 14:26 Andrew Pinski 2003-05-06 14:26 Wolfgang Bangerth 2003-05-06 14:09 bangerth 2003-05-06 8:26 Christian Ehrhardt 2003-05-05 14:34 bangerth 2003-05-05 13:36 khan_sanjay
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=20030506150600.13276.qmail@sources.redhat.com \ --to=pinskia@physics.uc.edu \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ /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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).