Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Brian Dessent <brian@dessent.net>
To: cygwin-patches@cygwin.com
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] fix spurious SIGSEGV faults under Cygwin
Date: Thu, 02 Feb 2006 17:42:00 -0000	[thread overview]
Message-ID: <43E24462.67E8F280@dessent.net> (raw)
In-Reply-To: <009001c6281e$5907ef60$a501a8c0@CAM.ARTIMI.COM>

Dave Korn wrote:

>   I'm having a conceptual difficulty here: Under what circumstances would you expect there *not* to be a debugger attached to the
> inferior to which the debugger is attached?  That's a bit zen, isn't it?

The code in question here runs many times in the normal course of any
Cygwin program -- debugger or no.  The idea behind guarding the call to
OutputDebugString() with "if (being_debugged())" was that the call to
IsDebuggerPresent() was cheaper than the call to OutputDebugString(),
and that a well-behaived, non-debug build of a binary should not
needlessly send tons and tons of nonsense to OutputDebugString unless
it's actually being debugged and there is something there to interpret
the nonsense.

Brian


  parent reply	other threads:[~2006-02-02 17:42 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'
2006-02-02 17:52               ` Dave Korn
2006-02-02 17:56                 ` 'Daniel Jacobowitz'
2006-02-02 17:42         ` Brian Dessent [this message]
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=43E24462.67E8F280@dessent.net \
    --to=brian@dessent.net \
    --cc=cygwin-patches@cygwin.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