Core dump analysis for a c++ binary

Question

Hello,
I tried to get stack trace of core generated by a C++ binary using "dbx" tool on Solaris Spark 5.9 as follows:
./WS5.0/bin/sparcv9/dbx) where
=>[1] __lwp_cond_broadcast(0x0, 0x6, 0x0, 0xffffffff, 0x4e310, 0xfd6b5970), at 0xfd720034
[2] walk(0xfd73c008, 0xffbecb30, 0x46, 0x7efefeff, 0x81010100, 0xfd71ff58), at 0xfd6b5a54
[3] walk(0xff172da8, 0xff172dc4, 0xf3, 0xff172dc4, 0x81010100, 0xff00), at 0xfd6b5cf8
[4] Token::UpdateImpl(0xffbedeb4, 0x0, 0xff172d9c, 0xd800, 0x7fffffff, 0xffff), at 0xff14f9cc
[5] 0xff1503e0(0xffbedeb4, 0xffbede9c, 0x0, 0x0, 0xff17137c, 0x0), at 0xff1503df
[6] 0xff153aac(0xffbedfd4, 0xff173544, 0xffbee070, 0xffbedf2c, 0xffbedf28, 0x0), at 0xff153aab
[7] 0xff1539e8(0xffbedfd4, 0xffbefc4c, 0xffbee070, 0x1, 0x4, 0x49), at 0xff1539e7
[8] RequestCGI::GetVariable(0xffbee084, 0xffbefc40, 0xffbee070, 0xff366f60, 0xfda72f54, 0x1), at 0xff366fac
[9] Service::GetRequest(0xffbef214, 0xfec146ac, 0xffbefc40, 0xfec1809d, 0xffbef9e4, 0xffbef9f8), at 0xfebb3208
[10] App::GetRequest(0x56a24, 0xfec17b74, 0xffbef32c, 0xffbef42c, 0xffbef44c, 0xffbef46c), at 0xfeba9630
[11] 0x1b5dc(0x56a20, 0xffbefc40, 0x7c00, 0x4cb3c, 0x4dc9c, 0xac00), at 0x1b5db
[12] main(0x1, 0xffbefdf4, 0xffbefdfc, 0x4c800, 0x0, 0x0), at 0xff364470
(/infra/workshop/ws5/SUNWspro/bin/../WS5.0/bin/sparcv9/dbx)
Can somebody help me in getting what is the "walk" sys-call/function?
Thanks in advance.
Best regareds,
Ram

Answer 1

It appears you are using WorkShop 5.0, which is more than 10 years old, and is no longer supported. Please do not use this hopelessly out-of-date software. In addition, it appears you are running on Solaris 9 (SunOS 5.9), which does not support Workshop 5.0.
To verify the software versions, run the command "CC -V" to get the compiler version (C++ 5.0 in WorkShop 5.0), and the command "uname -a" to verify the Solaris version.
The most recent version of Sun Studio (the more recent name for WorkShop) that supports Solaris 9 is Sun Studio 12. Please upgrade to Sun Studio 12 and rebuild your software. You can get it here:
[http://developers.sun.com/sunstudio/downloads/previous/ss12/]
To answer your question, "walk" is probably part of the stack walkback utility and would normally be suppressed by dbx. The mis-match between the dbx in WorkShop 5.0 and Solaris 9 might cause unusual behavior.