From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26077 invoked by alias); 18 May 2005 08:08:17 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 25459 invoked from network); 18 May 2005 08:07:53 -0000 Received: from unknown (HELO andromeda.onevision.de) (212.77.172.62) by sourceware.org with SMTP; 18 May 2005 08:07:53 -0000 Received: from [192.168.5.120] (oppenheim.onevision.de [192.168.5.120]) by andromeda.onevision.de (8.13.1/8.12.9/ROSCH/DDB) with ESMTP id j4I87OnR016719; Wed, 18 May 2005 10:07:24 +0200 Message-ID: <428AF788.5080603@onevision.de> Date: Wed, 18 May 2005 08:08:00 -0000 From: Roland Schwingel User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20040910 MIME-Version: 1.0 To: Christopher Faylor CC: gdb@sourceware.org Subject: Re: Stack unwinding on Windows with gdb 6.x (was: gdb stack trace problems (Addendum)) Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2005-05/txt/msg00176.txt.bz2 Hi... Christopher Faylor wrote on 17.05.2005 18:56:05: [...] > I use gdb to debug on Windows on a daily basis and I don't find myself > hampered by gdb's inability to backtrace out of system functions. It's > ability to do that has always been iffy. Well we are working on highly multithreaded applications and with all that native windows thread handling you always run into these problems with gdb 6.x. Especially when your try to track down a crash it is terrible. You won't get *any* useful stack trace. Whereas it was possible with 5.3. > So, as the windows maintainer, I have no immediate plans to try to > address this. If it is bothering you, however, then I'll certainly > review any patches that you submit. Thanks. I am definitely willing to do something on it but if I can get some pointers on how stack tracing works in gdb 6.x compared to 5.3 this would be extremely helpful. As of the fact that I am at present extremly busy with other things it can take until june until I can actively work on it, but when I have some pointers where I can read on how it internally works in gdb I already can make myself a bit more used to the internals of gdb. Roland