This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Debugging lto1, how?
- From: Rafael Espindola <espindola at google dot com>
- To: Steven Bosscher <stevenb dot gcc at gmail dot com>
- Cc: GCC Mailing List <gcc at gcc dot gnu dot org>
- Date: Tue, 29 Dec 2009 11:41:29 -0500
- Subject: Re: Debugging lto1, how?
- References: <571f6b510912290810u39bc3f10r6384cb3d79ed37c1@mail.gmail.com>
2009/12/29 Steven Bosscher <stevenb.gcc@gmail.com>:
> Hi,
>
> I am trying to see what is going on in lto1 for PR lto/42534. I can
> reproduce the reported ICE but I can't reproduce it inside gdb to see
> what is happening. Debugging lto1 is not trivial - just getting the
> arguments and input files right is hard.
>
> Apparently this is a known issue
> (http://gcc.gnu.org/ml/gcc/2009-11/msg00047.html).
>
> Could someone with experience in debugging lto1 perhaps add a HOWTO
> for this on the Wiki?
Have you been able to get the lto1 command line? I don't think I have
seen a case where a direct invocation of lto1 would fail but it would
work in gdb. Sounds like a memory problem, have you tried valgrind?
Getting the command line is annoying. In part because of the many
layers in part because of the use of @files.
gcc -v -save-temps should print you the necessary command line, no?
Are you using gold + plugin or collect2?
> Thanks,
>
> Ciao!
> Steven
>
Cheers,
--
Rafael Ãvila de EspÃndola