From: Lerele <lerele@champenstudios.com>
To: Khaled Jmal <khaledjmal@yahoo.fr>
Cc: gdb@sourceware.org
Subject: Re: i386 gdbserver for windows: break problem
Date: Wed, 21 Feb 2007 20:02:00 -0000 [thread overview]
Message-ID: <45DC8C8C.6040007@champenstudios.com> (raw)
In-Reply-To: <20070221170543.14860.qmail@web26306.mail.ukl.yahoo.com>
Khaled Jmal wrote:
>Hi all,
>
>I'm using gdbserver 6.6 and I compiled it for windows with mingw.
>It looks like the break is not working. The gdbserver doesn't react to CTRL-C
>Is this function implemented
>
>I tried to patch the gdbserver so that it polls the status when the application is running.
>With GenerateConsoleCtrlEvent I could stop the application but only if the application
>shares the same console as the gdbserver.
>
>Any help?
>
>
>Thanks,
>Khaled
>
>
>
>
The gdbserver for Win32 patch I submitted did not include that support.
I did work on that some months ago to let client gdb interrupt the
remotely debugged process, but never actually submitted the patch. It
did work somewhat, but the approach wasn't correct because the way I
handled interrupt support interfered too much with debugged process
execution, and it was somewhat buggy.
I know it's very annoying not to be able to interrupt remote process,
but I have not found time to implement that support correctly, sorry.
It's on my todo. I will do it eventually, if nobody else does first.
Leo.
>
>
>
>
>
>___________________________________________________________________________
>Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions !
>Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses
>http://fr.answers.yahoo.com
>
>
>
next prev parent reply other threads:[~2007-02-21 18:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-21 19:58 Khaled Jmal
2007-02-21 20:02 ` Lerele [this message]
2007-02-21 22:02 ` Michael Snyder
2007-02-22 12:27 ` Eli Zaretskii
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=45DC8C8C.6040007@champenstudios.com \
--to=lerele@champenstudios.com \
--cc=gdb@sourceware.org \
--cc=khaledjmal@yahoo.fr \
/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