From: Andrew Cagney <cagney@gnu.org>
To: Randolph Chung <randolph@tausq.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] rudimentary infrun debugging
Date: Fri, 05 Nov 2004 20:34:00 -0000 [thread overview]
Message-ID: <418BE3B9.8060605@gnu.org> (raw)
In-Reply-To: <20041105190530.GB7666@tausq.org>
Randolph Chung wrote:
> I've been using this for debugging infrun for some time. Dunno if it's
> suitable for inclusion.
>
> Thoughts? Is it too little? too verbose? Too ugly?
>
> (gdb) set debug infrun 1
> (gdb) step
> inferior: proceed(addr=ffffffff, signal=144, step=1)
> inferior: resume(step=1, signal=0)
> inferior_event: infwait_normal_state
> inferior_event: TARGET_WAITKIND_STOPPED
> inferior_event: stop_pc = 106f8
> inferior_event: trap expected
> inferior_event: stepping inside range [106f4-10708]
> inferior: resume(step=1, signal=0)
> inferior: prepare_to_wait
> inferior_event: infwait_normal_state
> inferior_event: TARGET_WAITKIND_STOPPED
> inferior_event: stop_pc = 106fc
> inferior_event: stepping inside range [106f4-10708]
> inferior: resume(step=1, signal=0)
> inferior: prepare_to_wait
> inferior_event: infwait_normal_state
> inferior_event: TARGET_WAITKIND_STOPPED
> inferior_event: stop_pc = 10700
> inferior_event: stepping inside range [106f4-10708]
> inferior: resume(step=1, signal=0)
> inferior: prepare_to_wait
> inferior_event: infwait_normal_state
> inferior_event: TARGET_WAITKIND_STOPPED
> inferior_event: stop_pc = 10704
> inferior_event: stepping inside range [106f4-10708]
> inferior: resume(step=1, signal=0)
> inferior: prepare_to_wait
> inferior_event: infwait_normal_state
> inferior_event: TARGET_WAITKIND_STOPPED
> inferior_event: stop_pc = 10708
> inferior_event: INSTRUCTION_NULLIFIED
> inferior: prepare_to_wait
> inferior_event: infwait_nullified_state
> inferior_event: TARGET_WAITKIND_STOPPED
> inferior_event: stop_pc = 106f4
> inferior_event: BPSTATE_WHAT_STOP_NOISY
> inferior: stop_stepping
>
>
> 2004-11-05 Randolph Chung <tausq@debian.org>
>
> * infrun.c (debug_infrun): New variable.
> (resume, proceed, wait_for_inferior): Annotate with debug messages.
> (handle_inferior_event, keep_going): Likewise.
> (_initialize_infrun): Register "set debug infrun" command.
Hmm, nice!
You'll need to add this to the gdb.texinfo documentation (it goes in
appendix), just post that separatly.
For the output, minor tweaks:
- prefix things with a single consistent "infrun: " (and if that makes
other prefixes redundant (e.g., "inferior: ") drop it - your call.
- that ``space before an lparen in function calls'' vis: ``` resume (...''.
- prefix addresses with 0x (I note you're spot on with using paddr_nz).
Andrew
next prev parent reply other threads:[~2004-11-05 20:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-05 19:05 Randolph Chung
2004-11-05 20:34 ` Andrew Cagney [this message]
2004-11-06 0:53 ` Randolph Chung
2004-11-06 1:09 ` Andrew Cagney
2004-11-06 1:29 ` Randolph Chung
2004-11-06 9:59 ` Eli Zaretskii
2004-11-08 16:50 ` Andrew Cagney
2004-11-08 17:20 ` Randolph Chung
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=418BE3B9.8060605@gnu.org \
--to=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=randolph@tausq.org \
/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