SEO

#1 (**permalink**) 01-16-2008, 06:47 PM

Hi,

I am debugging a problem using gdb on HPUX on Itanium processor system.
When I try to print backtrace of the stack, it doesn't print
arguments. This program is not compiled with -g options. I would
like to dump raw arguments(like register contents, current instruction
pointer, register values etc., debug at assembly level).

Thanks for the pointers.
Siva

#2 (**permalink**) 01-16-2008, 06:47 PM

Siva Kodiganti <siva.kodiganti@oracle.com> wrote:

> I am debugging a problem using gdb on HPUX on Itanium processor
> system. When I try to print backtrace of the stack, it doesn't
> print arguments. This program is not compiled with -g options. I
> would like to dump raw arguments(like register contents, current
> instruction pointer, register values etc., debug at assembly level).

I do not know that it would be substantially different, but you might
try wdb from HP. If there were mods required to get arguments and the
like wdb would likely have them first.

rick jones
--
oxymoron n, commuter in a gas-guzzling luxury SUV with an American flag
these opinions are mine, all mine; HP might not want them anyway...

feel free to post, OR email to raj in cup.hp.com but NOT BOTH...

#3 (**permalink**) 01-16-2008, 06:47 PM

The arguments on a stack traceback are only available from the debug
information generated with -g. While I appreciate Rick Jones pointing
you at WDB, that point is not different in WDB from other debuggers.

- Carl Burch
HP WDB Team

#4 (**permalink**) 01-16-2008, 06:48 PM

Siva Kodiganti (siva.kodiganti@oracle.com) wrote:
: This program is not compiled with -g options. I would
: like to dump raw arguments(like register contents, current instruction
: pointer, register values etc., debug at assembly level).

If you want to do it at the assembly level, use the frame command to
walk the stack and then use "info reg". Or print out $gr32 .. $gr39.
The current PC for each frame is on the bt stack trace.

#5 (**permalink**) 01-16-2008, 06:51 PM

You can always do "info registers" to get the register contents. "info
frame" also tells you where each stacked register is. Program counter can be
printed using $pc. It anyway shows up in the backtrace.

-Himabindu Vuppula

"Siva Kodiganti" <siva.kodiganti@oracle.com> wrote in message
news:dmiHd.32$p85.137@news.oracle.com...
> Hi,
>
> I am debugging a problem using gdb on HPUX on Itanium processor system.
> When I try to print backtrace of the stack, it doesn't print
> arguments. This program is not compiled with -g options. I would
> like to dump raw arguments(like register contents, current instruction
> pointer, register values etc., debug at assembly level).
>
> Thanks for the pointers.
> Siva

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

Dumping stacktrace on HPUX itanium using gdb