Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Randolph Chung <randolph@tausq.org>
To: Carl Burch <cdb@cup.hp.com>
Cc: gdb@sources.redhat.com,  brobecker@adacore.com,
	  dave@hiauly1.hia.nrc.ca
Subject: Re: [hpux] interesting but difficult to unwind code
Date: Sun, 11 Dec 2005 14:45:00 -0000	[thread overview]
Message-ID: <439C3B6A.7060503@tausq.org> (raw)
In-Reply-To: <200512091847.KAA08575@adlwrk03.cup.hp.com>

>    If you have our odump tool, "odump -comp a.out" will show you the 
> compiler and options used to build each object for a PA32 executable :

thanks.

>    There are two bits in the "struct unwind_table_entry" defined in
> config/pa/tm-hppa.h (at least in the WDB sources) that cover alloca() use
> and +Oentrysched use:
> 
>     unsigned int sched_entry_seq:1;     /* 25 */
> 		...
>     unsigned int alloca_frame:1;        /* 35 */
> 
> Unfortunately, even HP gdb doesn't print out those fields for a "maintenance
> print unwind" command.

I'll fix this this FSF gdb. Thanks for pointing this out!

Meanwhile with these pointers I've fixed the unwinding problem described 
previously in my local tree. Will do some more testing and send the 
patch to gdb-patches. Thanks for your help Carl.

randolph


  parent reply	other threads:[~2005-12-11 14:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-09 18:47 Carl Burch
2005-12-10  0:43 ` John David Anglin
2005-12-11 14:45 ` Randolph Chung [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-12-09  0:08 Randolph Chung
2005-12-09  0:44 ` John David Anglin
2005-12-09  3:33   ` Randolph Chung
2005-12-09  4:55     ` John David Anglin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=439C3B6A.7060503@tausq.org \
    --to=randolph@tausq.org \
    --cc=brobecker@adacore.com \
    --cc=cdb@cup.hp.com \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=gdb@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox