Matthias Klose wrote:
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.
I see. I still guess the problem was related to using `-g'.
A recent bug report from Emil Jerabek (see my reply in the other mail about emil7.pas) has lead Peter and me to a rather general problem with function inlining (which is done automatically with `-O3' but not `-O2' as you probably know). I'm not sure if the problem affects only debug info generation, but at least it does so to a large extent.
I'm now going to fix it, so you might want to try this example again with `-O3' with the next GPC version.
Frank