From: Andreas Schwab <schwab@suse.de>
To: Udma Catalin-Dan-B32721 <B32721@freescale.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: gdb : use of PTRACE_SINGLEBLOCK
Date: Thu, 11 Jul 2013 15:25:00 -0000 [thread overview]
Message-ID: <mvmip0hm84u.fsf@hawking.suse.de> (raw)
In-Reply-To: <FE751157F0442848A159F3AB4CB1F55B3E860A@039-SN1MPN1-005.039d.mgd.msft.net> (Udma Catalin-Dan-B's message of "Thu, 11 Jul 2013 15:05:36 +0000")
Udma Catalin-Dan-B32721 <B32721@freescale.com> writes:
> Do you know of any situation where gdb used PTRACE_SINGLEBLOCK?
`git log -SPTRACE_SINGLEBLOCK --remotes' didn't show anything.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
prev parent reply other threads:[~2013-07-11 15:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-11 15:07 Udma Catalin-Dan-B32721
2013-07-11 15:14 ` Luis Machado
2013-07-11 15:25 ` Andreas Schwab [this message]
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=mvmip0hm84u.fsf@hawking.suse.de \
--to=schwab@suse.de \
--cc=B32721@freescale.com \
--cc=gdb@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