From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26836 invoked by alias); 17 May 2005 08:40:01 -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 26635 invoked from network); 17 May 2005 08:39:49 -0000 Received: from unknown (HELO andromeda.onevision.de) (212.77.172.62) by sourceware.org with SMTP; 17 May 2005 08:39:49 -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 j4H8dk8u017130 for ; Tue, 17 May 2005 10:39:46 +0200 Message-ID: <4289AD9E.7060206@onevision.de> Date: Tue, 17 May 2005 08:40: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: gdb@sourceware.org Subject: Stack unwinding on Windows with gdb 6.x (was: gdb stack trace problems (Addendum)) Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2005-05/txt/msg00166.txt.bz2 Hi... I don't like to reply to my own messages but I don't want to let this to be fallen asleep again. In my eyes gdb 6.x is at present only of very limited use when debugging on windows mingw compiled executables because it cannot dump stack frames reliable. I know that the stack unwinder of gdb 6.x is of much better nature then the one of 5.3, but with 5.3 one could use gdb very good on windows to debug mingw code. So I think gdb 6.x should be able again to work on windows. So what can be done to fix this? Are there any pointers to find out how the current stack unwinder works compared to the old one. Maybe it would be possible to mix the 2 on windows. Thanks, Roland