From: 'Daniel Jacobowitz' <drow@false.org>
To: Dave Korn <dave.korn@artimi.com>
Cc: cygwin-patches@cygwin.com, gdb-patches@sourceware.org
Subject: Re: [patch] fix spurious SIGSEGV faults under Cygwin
Date: Thu, 02 Feb 2006 17:46:00 -0000 [thread overview]
Message-ID: <20060202174600.GA5696@nevyn.them.org> (raw)
In-Reply-To: <009401c62820$3ab87730$a501a8c0@CAM.ARTIMI.COM>
On Thu, Feb 02, 2006 at 05:43:51PM -0000, Dave Korn wrote:
> What I can't see is any point in gdb reading a variable from the
> inferior that tells gdb if there is a debugger attached to the
> inferior, because I can't see how gdb could read that variable except
> by attaching to the inferior, at which point the value in the
> variable should always be 'true', shouldn't it?
He wrote:
> If it turns out that it's expensive, I was thinking that the inferior
> could maintain this information in some variable, and just communicate
> its location to gdb once at startup, then gdb could simply read that
> variable in the process' memory before deciding whether to handle the
> fault.
"this information" does not refer to "if there is a debugger attached".
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-02-02 17:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 12:26 Brian Dessent
2006-02-02 16:00 ` Brian Dessent
2006-02-02 17:06 ` Christopher Faylor
2006-02-02 17:21 ` Brian Dessent
2006-02-02 17:30 ` Dave Korn
2006-02-02 17:38 ` Daniel Jacobowitz
2006-02-02 17:43 ` Dave Korn
2006-02-02 17:46 ` 'Daniel Jacobowitz' [this message]
2006-02-02 17:52 ` Dave Korn
2006-02-02 17:56 ` 'Daniel Jacobowitz'
2006-02-02 17:42 ` Brian Dessent
2006-02-02 17:47 ` Dave Korn
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=20060202174600.GA5696@nevyn.them.org \
--to=drow@false.org \
--cc=cygwin-patches@cygwin.com \
--cc=dave.korn@artimi.com \
--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