This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [Patch] Win32 gdbserver new interrupt support, and attach to process fix.



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.




Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]