This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: flag to dump core on error


On Wed, Feb 12, 2003 at 03:23:26PM -0500, Phil Edwards wrote:
> On Wed, Feb 12, 2003 at 11:15:35AM +0100, Gabriel Dos Reis wrote:
> > Geoffrey Keating <gkeating@apple.com> writes:
> > 
> > | Sometimes I hit a bug that depends on the exact memory layout,
> > | including environment variables provided by make or the rest of the
> > | build system, and my usual procedure is to write a program 'fake-gcc'
> > | that prints out the environment and then another one that starts GCC
> > | with exactly that environment.  That's a lot of work.  I'd much rather
> > | have a flag that I could restart the build with and get a
> > | coredump---the same compile wouldn't fail, but chances are something
> > | will.
> > | 
> > | Thus, -dH (because a-h and A-G were taken).
> > 
> > :-)  Too cute for me to understand.  I would have prefered averbose flags.
> 
> Yeah, I think -d is getting overloaded here.  There's a difference between
> "dump" as in "dump rtl pass number 17" (most -d flags) and "dump" as in
> "coredump".
> 
> It's a really good idea, though.  Thanks for adding this.

Maybe we need to start using --long-options for dump flags?

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]