Port-vax archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Native build failure...

Matt Thomas wrote:
On Jul 15, 2010, at 11:25 AM, Johnny Billquist wrote:

Anyone having any idea?

This already when building tools...

nbgmake[1]: Leaving directory `/usr/obj/tools/gcc/build/fixincludes'
nbgmake[1]: Entering directory `/usr/obj/tools/gcc/build/gcc'
[1]   Segmentation fault (core dumped) (cd ./gcc && /us...
nbgmake: *** [install-gcc] Error 139

seem to remember you need to up the default stack size

It does not seem to be a problem with the stack size.
I've tried looking a bit more at it, although not entirely successful, since the build procedure is so convoluted and complex that it's hard for me to follow.

But anyway, what I have found out so far is that:
o it's nbgmake that craches with a segfault, not gcc.
o it crashes when doing the install of gcc. It has already successfully built the whole thing.
o I've tried with small and big stacksizes, without it making a difference.
o the routine in nbgmake it seems to crash in is update_file

I've tried looking through that routine, but the assembler output I see in objdump is just cryptic. Probably atleast partly because it's been through the optimizer.

If I read things right, it's one of these two lines wich cause the segfault though:
     ce1:       c8 50 ad d8     bisl2 r0,0xffffffd8(fp)
     ce5:       e8 a6 0d 05     blbs 0xd(r6),cee <update_file+0x428>

not that I can understand why...

Anyone have any ideas?


Johnny Billquist                  || "I'm on a bus
                                  ||  on a psychedelic trip
email: bqt%softjar.se@localhost             ||  Reading murder books
pdp is alive!                     ||  tryin' to stay hip" - B. Idol

Home | Main Index | Thread Index | Old Index