On 31 Aug 2011, at 17:34, Arnaud Charlet wrote:
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_PROTECTION_FAILURE at address: 0x00000000
0x001c4fa0 in lib__writ__write_ali ()
(gdb) bt
#0 0x001c4fa0 in lib__writ__write_ali ()
#1 0x0036799a in _ada_gnat1drv ()
#2 0x000305f5 in gnat_parse_file ()
I just triple checked, and revision 178381 is OK for me on
x86_64-unknown-linux-gnu.
Unfortunately without debug info, the above traceback isn't
giving much info.
Just a shot in the dark, can you try to pinpoint at which revision
things started to break? That'd be useful.
In particular I'd be curious to know if revision 178376 has the
failure or not.
different failure;
built with BOOT_CFLAGS="-O0 -g" ..
.. it fails debug-compare (ada/exp_ch6.o).
There are a lot of seemingly innocuous code differences (nop
insertions) masking whatever the real problem is (difficult to compare
because of the number of trivial differences).
If I touch compare and continue the bootstrap if fails building the
native tools with a gnatmake internal error
(SYSTEM_ASSERTIONS.ASSERT_FAILURE) namet.adb line 675 -- but that's a
target-specific file, right?
===
... FWIW, I find debugging ada bootstrap problems especially
intractable (any hints/advice on good techniques would be most
welcome) ....
.... I've yet to succeed in getting powerpc-darwin9 (trunk) to
bootstrap .. :-(
(although with some jiggery-pokery it is possible to bootstrap 4.6 on
it.)
Same for revision 178311
will set this going .. prob. tomorrow before a report.
----
Also - I don't know that Darwin is the best platform for test here --
it's probably the least exercised ... so other people might wish to
chime in....
cheers
Iain
