|
From: Fabio M. <fab...@gm...> - 2005-03-23 19:15:16
|
Yes I did return an int value from main.... But I double checked it now and the error doesn't appear anymore. How odd... On Wed, 23 Mar 2005 17:37:42 GMT, Tom Hughes <to...@co...> wrote: > In message <171...@ma...> > Fabio Margarido <fab...@gm...> wrote: > > > I've now upgraded to valgrind2.4.0-rc4 and tried to run my program > > which showed the glibc bugs I'd mentioned before (with 2.2.0) and now > > it shows another error message: > > > > ==7483== Syscall param exit_group(exit_code) contains uninitialised byte(s) > > ==7483== at 0x1B9BACB4: _Exit (in /lib/tls/libc-2.3.4.so) > > ==7483== by 0x1B944E79: __libc_start_main (in /lib/tls/libc-2.3.4.so) > > ==7483== by 0x8048940: ??? (start.S:119) > > > > Just thought I'd mention it... > > Did you return a defined value from main? You do know that main > should return int and not void I assume? > > The C library should just be passing whatever you returned from > main to the exit_group system call as the exit code, so if it is > undefined that most likely originates in your program. It could > be a bug in libc of course, but that seems unlikely in this case. > > Tom > > -- > Tom Hughes (to...@co...) > http://www.compton.nu/ > > ------------------------------------------------------- > This SF.net email is sponsored by Microsoft Mobile & Embedded DevCon 2005 > Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows > Embedded(r) & Windows Mobile(tm) platforms, applications & content. Register > by 3/29 & save $300 http://ads.osdn.com/?ad_id=6883&alloc_id=15149&op=click > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users > |