From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19186 invoked by alias); 5 Aug 2013 11:25:12 -0000 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 Received: (qmail 19147 invoked by uid 89); 5 Aug 2013 11:25:12 -0000 X-Spam-SWARE-Status: No, score=1.2 required=5.0 tests=AWL,BAYES_50 autolearn=ham version=3.3.1 Received: from Unknown (HELO outdoor.onevision.de) (212.77.172.51) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Mon, 05 Aug 2013 11:25:10 +0000 Received: from sanders.onevision.de (moonrace [212.77.172.62]) by outdoor.onevision.de (8.14.3/8.13.7/ROSCH/DDB) with ESMTP id r75BOqpI012365; Mon, 5 Aug 2013 13:24:57 +0200 Received: from [192.168.5.32] ([192.168.5.32]) by sanders.onevision.de (Lotus Domino Release 8.5.3) with ESMTP id 2013080513244773-3821 ; Mon, 5 Aug 2013 13:24:47 +0200 Message-ID: <51FF8B7F.8010505@onevision.de> Date: Mon, 05 Aug 2013 11:25:00 -0000 From: Roland Schwingel User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2 MIME-Version: 1.0 To: Tristan Gingold , Pedro Alves CC: Joel Brobecker , "gdb-patches@sourceware.org ml" Subject: Re: [RFA] Windows x64 SEH unwinder (v2) Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=ISO-8859-15; format=flowed X-SW-Source: 2013-08/txt/msg00134.txt.bz2 Hi Tristan... gdb-patches-owner@sourceware.org wrote on 08.07.2013 12:55:21: > Hello, > > this is the second version of the patch we submitted in January. > I have rewritten amd64_windows_frame_decode_epilogue according to the > very serious review and comments from Pedro. > > Tristan. Today I gave your SEH unwinder patch a try. I hopped to get an issue from 2005 resolved. (See: http://sourceware.org/ml/gdb/2005-04/msg00113.html) I compiled my test C code from this post using GCC 4.8.1 for x64 windows with no special options beside of a single -g. Stack frames are way better... Congratulations... But: When inspecting frames I see problems showing the content of variables. I cannot look into any of the applications vars. gdb just shows eg: #1: 0x0000000000401577 in func4 (num=) at gdb_crash.c:26 also a "p num" show the same error. Did I do something wrong? Is there a hidden trick that needs to be applied to get this going that I couldn't find from reading the patch? Thanks for your help, Roland