Re: porting problem: segfault when compiling programs that call malloc

2007-09-14 Thread Jim Wilson
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 w

Re: porting problem: segfault when compiling programs that call malloc

2007-09-14 Thread Ian Lance Taylor
"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.

Re: porting problem: segfault when compiling programs that call malloc

2007-09-14 Thread Tomas Svensson
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

Re: porting problem: segfault when compiling programs that call malloc

2007-09-13 Thread Ian Lance Taylor
"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