Using the gdb32/64 debugger on Intanium HPUX 11.11

To give you some perspective, I am not a Unix C programmer. We have a vendor application we run/support on our Itanium Servers that is periodically failing and producing core files. Our vendor says the cores are meaningless unless we produce a stack trace with our debugger and send them the output. We are not familiar with our new tools since switching from TRU64.

We used to run stack traces on our old alphas using decladebug...we have never done this with gdb. I am looking for some examples..proper syntax & necessary parameters... (in fairly simple terms...) on how to produce a stack trace using this new tool.

Any help on this would be appreciated.

Thank You.
GeekManAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

ahoffmannCommented:
> Our vendor says the cores are meaningless unless we produce a stack trace with our debugger and send them the output.

does your vendor really know what he's talking about?
a UNIX core file contains the stack trace (and much more ...)
if you start the debugger with the corefile, you'll see it
GeekManAuthor Commented:
Apparently, they can't run a debugger in one environment against a core file from another. Our past experience in TRU64 has been that we take a 600 meg core and the debugger outputs  3-4kb worht of text  that specifically addreses what the problem was with the code.

This little 3-4kb worth of text is what they are wanting now.
ahoffmannCommented:
sometimes a simple
  strings core
also helps ...

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Artysystem administratorCommented:
Running gdb specially for backtraces:

gdb /usr/bin/yourprogram /usr/bin/yourprogram.core
bt

that's all.
/usr/bin/yourprogram is executable program, that have failed
/usr/bin/yourprogram.core is a core file
bt is a command of 'gdb' debugger to get a backtrace, please wait while gdb loads core file (it takes time for 600M core).
DineshJolaniaCommented:
Not even "bt" is needed
gdb  "exefile" "corefile" will  itself start with call stack.
Even if you are using gdb, if  your exe is not  compiled with -g(which most of the time happens with third party vendors) , you may not get a simple stack(It will be a simple  hexadecimal+ mangled symbols).
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
System Programming

From novice to tech pro — start learning today.