core dump related to atoi() of libC library?

Need a help!

One of the processes is generating core dump ocassionally (running on Solaris 5.8 and Sun Workshop Compiler 5) with the following dbx stack trace.

=>[1] _libc_write(0x0, 0x6, 0x0, 0xffffffff, 0x4e310, 0xfd6b5970), at 0xfd720034

[2] addsev(0xfd73c008, 0xffbecb30, 0x47, 0x7efefeff, 0x81010100, 0xfd71ff58),

at 0xfd6b5a54

[3] atoi(0xff172e20, 0xff172e3c, 0x118, 0xff172e3c, 0x81010100, 0xff00), at 0x

fd6b5cf8

[4] TStr::UpdateUniImpl(0xffbedeb4, 0x3, 0xff172d9c, 0xd800, 0x7fffffff

, 0xffff), at 0xff14fa14

[5] TStr::Index(0xffbedeb4, 0xffbede9c, 0x0, 0x0, 0xff17137c, 0x0), at 0xff

1503e0

[6] TEnv::GetLocation(0xffbedfd4, 0xff173544, 0xffbee070, 0xffbedf2c,

0xffbedf28, 0x0), at 0xff153aac

Is this refer to some bug in libC ?

Thanks in advance.

Best regards,

[877 byte] By [mailtork1a] at [2007-11-27 5:07:19]
# 1

The atoi() function is in /lib/libc.so.1, the basic Solaris and C runtime support library.

I strongly doubt that you have hit a bug in atoi. It is much more likely that the error is in the user-level code. For example, the pointer passed to atoi() is probably not valid.

The argument values shown in a stack trace are not accurate when the code is optimized. You probably need to run the code under dbx and look at what happens in TStr::UpdateUniImpl where it calls atoi.

clamage45a at 2007-7-12 10:26:23 > top of Java-index,Development Tools,Solaris and Linux Development Tools...