gdb and dbx question

[P L]

I have an app on Solaris 2.8 that cored. The app was compiled with -g
on Solaris 2.6. Both dbx and gdb seems to report incorrect stack
traces. In dbx report, one function takes NULL as arg, which according
to the source code, should return immediately; yet dbx shows quite a
few stack frames on top of that function. In gdb report, some
functions take arguments that are never passed to the functions
according to the source code. On the other hand, dbx and gdb report
similar but different stack pointers, and similar but different
function arguments. They both reports the same functions in the stack
trace. Can someone shed some light?

BTW, I googled the Internet but didn't find a faq on dbx or gdb. Does
any one knows anything about it? Thanks. -PL

 

[Mark McIntyre]

I have an app on Solaris 2.8 that cored. The app was compiled with -g
on Solaris 2.6. Both dbx and gdb seems to report incorrect stack
traces.

try comp.unix.programming, or a group specialising in whtever your
compiler is. unix toolsets are offtopic here.

BTW, I googled the Internet but didn't find a faq on dbx or gdb.

Not trying to be funny, but I found several by googling. I'm not
saying they'd have answered your questions but they're out there.