From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11232 invoked by alias); 5 Mar 2007 20:34:43 -0000 Received: (qmail 11224 invoked by uid 22791); 5 Mar 2007 20:34:43 -0000 X-Spam-Check-By: sourceware.org Received: from 164.Red-80-36-45.staticIP.rima-tde.net (HELO jupiter.champenstudios.com) (80.36.45.164) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 05 Mar 2007 20:34:40 +0000 Received: from [192.168.1.132] ([192.168.1.132]) by jupiter.champenstudios.com (8.13.5/8.13.5) with ESMTP id l25KNDvR018950; Mon, 5 Mar 2007 21:23:13 +0100 Message-ID: <45EC7CBE.3090305@champenstudios.com> Date: Mon, 05 Mar 2007 20:34:00 -0000 From: Lerele User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) MIME-Version: 1.0 To: Lerele CC: Pedro Alves , gdb-patches@sourceware.org Subject: Re: [Patch] Win32 gdbserver new interrupt support, and attach to process fix. References: <45DF7E27.10102@champenstudios.com> <45E211A5.6080905@portugalmail.pt> <45EB4D5A.7070703@champenstudios.com> <45EB6AC8.3090307@portugalmail.pt> <45EC1815.2000002@champenstudios.com> In-Reply-To: <45EC1815.2000002@champenstudios.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2007-03/txt/msg00046.txt.bz2 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.