From: Lerele <lerele@champenstudios.com>
To: Lerele <lerele@champenstudios.com>
Cc: Pedro Alves <pedro_alves@portugalmail.pt>, gdb-patches@sourceware.org
Subject: Re: [Patch] Win32 gdbserver new interrupt support, and attach to process fix.
Date: Mon, 05 Mar 2007 20:34:00 -0000 [thread overview]
Message-ID: <45EC7CBE.3090305@champenstudios.com> (raw)
In-Reply-To: <45EC1815.2000002@champenstudios.com>
Lerele wrote:
>
> It's not only that I'm concerned about it, personally I just find it
> unacceptable for a debugger to do that kind of thing (or Windows
> anyway); user code (or standard windows dlls) can do plainly anything
> in DllEntry for instance, that can make debugged code behave very
> differently.
Well, that "unacceptable" sounded a bit hard.
I meant that when I debug a program I expect the debugger not to fail in
catching the same bugs I get when running it in standalone, and creating
threads for interrupting the program, I think may (or may not,
possibility is there) make it worse for the debugger to be able to catch
those bugs (am I wrong?). If it fails in doing so, it's useless, and
makes me search for other strategies, tools, or whatever to catch the bug.
next prev parent reply other threads:[~2007-03-05 20:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-23 23:52 Lerele
2007-02-24 12:07 ` Eli Zaretskii
2007-02-24 13:03 ` Lerele
2007-02-24 14:07 ` Eli Zaretskii
2007-02-24 15:23 ` Lerele
2007-02-24 19:10 ` Eli Zaretskii
2007-02-24 21:19 ` Pedro Alves
2007-02-24 21:44 ` Andreas Schwab
2007-02-24 23:35 ` Lerele
2007-02-25 0:15 ` Daniel Jacobowitz
2007-02-25 1:57 ` Pedro Alves
2007-02-25 22:46 ` Pedro Alves
2007-03-04 22:53 ` Lerele
2007-03-05 0:56 ` Pedro Alves
2007-03-05 1:21 ` Pedro Alves
2007-03-05 13:17 ` Lerele
2007-03-05 20:34 ` Lerele [this message]
2007-03-05 20:44 ` Pedro Alves
2007-03-06 0:04 ` Pedro Alves
2007-03-06 20:39 ` Pedro Alves
2007-03-06 22:18 ` Lerele
2007-03-06 23:22 ` Pedro Alves
2007-03-05 12:44 ` Daniel Jacobowitz
2007-03-05 20:30 ` Lerele
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=45EC7CBE.3090305@champenstudios.com \
--to=lerele@champenstudios.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro_alves@portugalmail.pt \
/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