From: Andreas Schwab <schwab@suse.de>
To: gdb-patches@sourceware.org
Subject: Re: [rfc, rfa/doc] Multi-threaded watchpoint improvements
Date: Wed, 16 Apr 2008 23:18:00 -0000 [thread overview]
Message-ID: <jeabjtcsfb.fsf@sykes.suse.de> (raw)
In-Reply-To: <20080416224910.GA3716@caradoc.them.org> (Daniel Jacobowitz's message of "Wed, 16 Apr 2008 18:49:10 -0400")
Daniel Jacobowitz <drow@false.org> writes:
> Covering my ass out of the way, can you be a little more specific?
> What CPU/kernel, any useful debug logs you have, et cetera.
2.6.25-rc9 on G5.
infrun: wait_for_inferior (treat_exec_as_sigtrap=1)
infrun: infwait_normal_state
infrun: TARGET_WAITKIND_STOPPED
infrun: stop_pc = 0x40015c60
infrun: quietly stopped
infrun: stop_stepping
infrun: resume (step=0, signal=0)
infrun: wait_for_inferior (treat_exec_as_sigtrap=1)
infrun: infwait_normal_state
infrun: TARGET_WAITKIND_STOPPED
infrun: stop_pc = 0x40015c60
infrun: quietly stopped
infrun: stop_stepping
infrun: proceed (addr=0xffffffff, signal=0, step=0)
infrun: resume (step=0, signal=0)
infrun: wait_for_inferior (treat_exec_as_sigtrap=0)
infrun: infwait_normal_state
infrun: TARGET_WAITKIND_STOPPED
infrun: stop_pc = 0x4000f0bc
infrun: BPSTAT_WHAT_CHECK_SHLIBS
infrun: no stepping, continue
infrun: resume (step=1, signal=0)
infrun: prepare_to_wait
infrun: infwait_normal_state
infrun: TARGET_WAITKIND_STOPPED
infrun: stop_pc = 0x4000f0c0
infrun: no stepping, continue
infrun: resume (step=0, signal=0)
infrun: prepare_to_wait
infrun: infwait_normal_state
infrun: TARGET_WAITKIND_STOPPED
infrun: stop_pc = 0x4000f0bc
infrun: BPSTAT_WHAT_CHECK_SHLIBS
infrun: no stepping, continue
infrun: resume (step=1, signal=0)
infrun: prepare_to_wait
infrun: infwait_normal_state
infrun: TARGET_WAITKIND_STOPPED
infrun: stop_pc = 0x4000f0c0
infrun: no stepping, continue
infrun: resume (step=0, signal=0)
infrun: prepare_to_wait
infrun: infwait_normal_state
infrun: TARGET_WAITKIND_STOPPED
infrun: stop_pc = 0x100004ac
infrun: STOPPED_BY_WATCHPOINT
infrun: prepare_to_wait
infrun: infwait_nonstep_watch_state
infrun: TARGET_WAITKIND_STOPPED
infrun: stop_pc = 0x100004b0
infrun: random signal 5
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2008-04-16 23:05 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-16 18:40 Daniel Jacobowitz
2007-09-22 9:03 ` Eli Zaretskii
2007-09-22 14:04 ` Daniel Jacobowitz
2007-09-22 14:13 ` Eli Zaretskii
2007-09-22 15:37 ` Daniel Jacobowitz
2007-09-22 15:46 ` Eli Zaretskii
2007-09-22 18:28 ` Daniel Jacobowitz
2007-10-01 0:20 ` Daniel Jacobowitz
2007-10-24 14:59 ` Luis Machado
2007-10-24 16:00 ` Daniel Jacobowitz
2007-10-24 16:42 ` Luis Machado
2007-10-24 16:51 ` Daniel Jacobowitz
2007-10-24 18:08 ` Luis Machado
2007-10-24 18:20 ` Daniel Jacobowitz
2008-04-16 22:57 ` Andreas Schwab
2008-04-16 23:05 ` Daniel Jacobowitz
2008-04-16 23:18 ` Andreas Schwab [this message]
2008-04-17 0:25 ` Daniel Jacobowitz
2008-04-17 9:52 ` Andreas Schwab
2008-04-17 9:59 ` Andreas Schwab
2008-04-17 10:17 ` Andreas Schwab
2008-04-17 14:53 ` Daniel Jacobowitz
2008-04-20 2:35 ` Andreas Schwab
2008-04-23 11:55 ` Andreas Schwab
2008-04-23 19:46 ` Eli Zaretskii
2008-05-01 19:30 ` Daniel Jacobowitz
2008-05-01 19:50 ` Luis Machado
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=jeabjtcsfb.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=gdb-patches@sourceware.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