Frank Heckenbach writes:
Matthias Klose wrote:
Cannot access memory at address 0xd0028038 (gdb) list 1592 tree c; 1593 { 1594 unsigned HOST_WIDE_INT high = TREE_INT_CST_HIGH (c); 1595 unsigned HOST_WIDE_INT low = TREE_INT_CST_LOW (c); 1596 int excess = (3 - (HOST_BITS_PER_WIDE_INT % 3)); 1597 int width = TYPE_PRECISION (TREE_TYPE (c)); 1598 1599 /* GDB wants constants with no extra leading "1" bits, so 1600 we need to remove any sign-extension that might be 1601 present. */
That's another bug now (at least another one than the one you sent me the last gdb log about (in private mail) which the patch I sent was for -- actually I'm slightly confused; I'm not sure if we're talking about one or several problems at all).
I can't reproduce this problem -- perhaps you can me a more detailed gdb output (including, e.g., `i s').
was trying with -O2 instead of -O3 to get more information ... and the file compiled now.
Anyway, I see you're using `-g'. Maybe that's the problem. It's a known issue (and listed in our known bugs list) that the debug info generation is quite unstable (AFAICS, that's mostly a backend problem, so I'm not sure if I can easily fix it, even if we find the cause of the crash ...). So, perhaps you'll just have to use no `-g' (e.g., `RTSFLAGS=-g0', and `EXTRA_PFLAGS=-g0' when running the test suite).
I'll try and post the results