On Tue, Dec 29, 2009 at 5:41 PM, Rafael Espindola <espind...@google.com> wrote: > 2009/12/29 Steven Bosscher <stevenb....@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?
I have the lto1 command line, yes. But that gives a different failure. When run from gcc, lto1 crashes with an ICE, and when I run lto1 standalone, it crashes with an error reading a hex number. > gcc -v -save-temps should print you the necessary command line, no? Yes. > Are you using gold + plugin or collect2? collect2. T.i.a. for any help you can give :-) Ciao! Steven
