On 13 Sep 2007 13:45:21 -0700, Ian Lance Taylor [EMAIL PROTECTED] wrote:
valreg is set around line 2564 of calls.c. It shouldn't be zero at
line 2787. Unless you have an malloc function with a return type of
void, which seems dubious.
Ok, do you have any idea about what might cause this to
Tomas Svensson [EMAIL PROTECTED] writes:
On 13 Sep 2007 13:45:21 -0700, Ian Lance Taylor [EMAIL PROTECTED] wrote:
valreg is set around line 2564 of calls.c. It shouldn't be zero at
line 2787. Unless you have an malloc function with a return type of
void, which seems dubious.
Ok, do
Tomas Svensson wrote:
Ok, do you have any idea about what might cause this to happen? Could
it be something wrong with exception handling or dwarf2 debugging
output? Or possibly varargs handling? I am complete lost here
unfortunately... Other function calls work just fine.
Build any port that
I am porting gcc to a new architecture, and have yet another problem
that I've been staring at for far too long now.
Whenever I compile a program that calls malloc, GCC crashes with:
/cygdrive/c/home/risc/src/gcc-4.1.2/gcc/unwind-dw2-fde.c: In function
'__register_frame':
Tomas Svensson [EMAIL PROTECTED] writes:
I am porting gcc to a new architecture, and have yet another problem
that I've been staring at for far too long now.
Whenever I compile a program that calls malloc, GCC crashes with:
/cygdrive/c/home/risc/src/gcc-4.1.2/gcc/unwind-dw2-fde.c: In
