From: Pierre Muller <muller@cerbere.u-strasbg.fr>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Add handling of Ctrl-Break for win32 native target.
Date: Mon, 04 Feb 2002 09:41:00 -0000 [thread overview]
Message-ID: <4.2.0.58.20020204181649.021ecb40@ics.u-strasbg.fr> (raw)
In-Reply-To: <20020204165240.GA8850@redhat.com>
At 17:52 04/02/2002 , vous avez écrit:
>On Mon, Feb 04, 2002 at 04:04:47PM +0100, Pierre Muller wrote:
> >2002-02-04 Pierre Muller <muller@ics.u-strasbg.fr>
> > win32-nat.c (handle_exception): Handle Ctrl-Break exception.
> >
>
>Looks good. Please check it in.
I tried, but I can't get the lock for /cvs/src/src/gdb
cvs server: [09:25:31] waiting for muller's lock in /cvs/src/src/gdb
cvs server: [09:26:01] waiting for muller's lock in /cvs/src/src/gdb
I am not sure that I understand this message correctly:
I am waiting until I can get a lock for muller (i.e. myself)
or is there some zombie processs somewhere on the cvs server?
>I'm looking forward to the patch to handle the pass state.
The main problem is that this will only partially work because of a known bug
in the win32 API:
Extracted from
http://www.microsoft.com/msj/defaultframe.asp?page=/msj/0898/bugslayer0898.htm&nav=/msj/0898/newnav.htm
There are a couple of issues to remember when using SetUnhandledExceptionFilter.
The first is that any exception filter that you set cannot be debugged. This is a known bug.
Knowledge Base article Q173652 says that under a debugger the process wide filter is not called.
This can be a bit of a pain, but in a C++ program you can just use your function in a regular SEH exception
filter to debug it. If you look at the CH_TEST.CPP test program, which is part of this month's source code
(Aug98Bugslayer.exe ), this is exactly what I did to debug it.
An alternative is to use a kernel debugger like WinDBG to get around this limitation.
But I don't really know if Cygwin library uses SetUnhandledExceptionFilter
(I suspect it does as my patch does not work as intended...).
I will send a [RFC] when all seems ready, even if it does not fully work...
Pierre Muller
Institut Charles Sadron
6,rue Boussingault
F 67083 STRASBOURG CEDEX (France)
mailto:muller@ics.u-strasbg.fr
Phone : (33)-3-88-41-40-07 Fax : (33)-3-88-41-40-99
next prev parent reply other threads:[~2002-02-04 17:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-04 7:05 Pierre Muller
2002-02-04 7:09 ` Eli Zaretskii
2002-02-04 7:20 ` Pierre Muller
2002-02-04 8:58 ` Christopher Faylor
2002-02-04 8:59 ` Eli Zaretskii
2002-02-04 8:52 ` Christopher Faylor
2002-02-04 9:41 ` Pierre Muller [this message]
2002-02-04 12:54 ` Christopher Faylor
2002-02-05 4:49 ` Pierre Muller
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=4.2.0.58.20020204181649.021ecb40@ics.u-strasbg.fr \
--to=muller@cerbere.u-strasbg.fr \
--cc=gdb-patches@sources.redhat.com \
/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