Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Joel Brobecker <brobecker@gnat.com>,
	Michael Elizabeth Chastain <mec@shout.net>
Cc: gdb-patches@sources.redhat.com
Subject: Time for a HP/PA hackathon?
Date: Wed, 11 Feb 2004 17:05:00 -0000	[thread overview]
Message-ID: <402A60C6.7060904@gnu.org> (raw)

Joel, Michael,

Would either of you be able to do a HP/PA build with the "0" here:

>   /* Frame unwind methods.  */
> #if 0

     // add this
     set_gdbarch_unwind_dummy_id (gdbarch, "hack function that returns 
null_frame_id for the dummy id");

> #else
>   set_gdbarch_deprecated_saved_pc_after_call (gdbarch, hppa_saved_pc_after_call

changed to a "1" and add an extra line, and then try that GDB to see 
what happens?

- Does it start?
There's a good chance GDB will panic during initialization ...

- If it starts, the output from:
(gdb) maint print architecture architecture
(gdb) shell grep -i deprecated architecture
I'm looking to see if/why legacy_frame_p() returns true/false (did that 
#if 1 really work?)

- what happens when:
./gdb .../advance
(gdb) break main
(gdb) run
(gdb) next ...
is executed.  I'm looking to see how/where GDB panics when stepping - 
this is testing the code's ability to unwind the PC register.

- what happens when
./gdb .../advance
(gdb) break func
(gdb) run
(gdb) advance func3
(it should end up in main)
I'm looking to see if/how GDB is correctly unwinding frame IDs - this is 
testing the code's ability to keep a frame ID constant across a function.

Andrew


             reply	other threads:[~2004-02-11 17:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-11 17:05 Andrew Cagney [this message]
2004-02-13 16:29 Michael Elizabeth Chastain
2004-02-13 16:54 ` Andrew Cagney
2004-02-13 18:13 Michael Elizabeth Chastain
2004-02-13 18:32 ` Elena Zannoni
2004-02-13 18:48   ` Andrew Cagney
2004-02-13 22:39 Michael Elizabeth Chastain
2004-02-14  2:01 ` Andrew Cagney
2004-02-14  3:14 Michael Elizabeth Chastain
2004-02-14 15:54 ` Andrew Cagney
2004-02-14 20:00 Michael Elizabeth Chastain
2004-02-15  1:20 ` Daniel Jacobowitz

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=402A60C6.7060904@gnu.org \
    --to=cagney@gnu.org \
    --cc=brobecker@gnat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec@shout.net \
    /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