From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15423 invoked by alias); 1 Jun 2012 08:18:36 -0000 Received: (qmail 15405 invoked by uid 22791); 1 Jun 2012 08:18:32 -0000 X-SWARE-Spam-Status: No, hits=-0.2 required=5.0 tests=AWL,BAYES_50,TW_BT,TW_DB X-Spam-Check-By: sourceware.org Received: from outdoor.onevision.de (HELO outdoor.onevision.de) (212.77.172.51) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 01 Jun 2012 08:18:18 +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 q518I9ca023235; Fri, 1 Jun 2012 10:18:14 +0200 Received: from [192.168.5.32] ([192.168.5.32]) by sanders.onevision.de (Lotus Domino Release 8.5.1FP3) with ESMTP id 2012060110180444-45228 ; Fri, 1 Jun 2012 10:18:04 +0200 Message-ID: <4FC87ABC.3080907@onevision.com> Date: Fri, 01 Jun 2012 08:18:00 -0000 From: Roland Schwingel User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: insight@sourceware.org, Gene Smith Subject: Re: mingw versions working Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=ISO-8859-15; format=flowed Mailing-List: contact insight-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sourceware.org X-SW-Source: 2012-q2/txt/msg00044.txt.bz2 Hi Gene, > I also rebuilt a previous version I made for fedora that used an > insight > snapshot from 2011 but without the tcl/tk/itcl, but using the system > versions. It also used the gdb files (except gdbtk which are still > insight's own) from Codesourcery. This almost works on windows (now > using bundled tcl/tk/itcl) but I can't set breakpoints with the > mouse. It might that the gdbtk code you are using is not matching the breakpoint handling code in the underlying Codesourcery gdb. > However, this mingw version containing codesourcery's gdb > (version 7.2) > still has one advantage over the the pure insight described in first > paragraph: when an ISR is entered the stack display shows the > task level > context that the ISR was called from like this: > > main() > fn1() > fun2() > > myIsr() > isrSub() > > The linux build also shows the this same stack/backtrace display > (also can set bp's with mouse in linux version). > But the "pure" insight > version stack display will look something like this: > > ?? > ?? > myIsr() > isrSub() > > I have looked around but don't see this listed anywhere as > an improved feature in gdb or codesourcery's version of > gdb. But I find it useful and wonder what it would take > to add this to the pure insight version? I don't believe (from my stomach) that the problem here comes from insight itself. Stack unwinding is done using gdb's facilities. Have you tried a commandline mingw gdb (built from the very same code base) and did you issue a "bt" command there. Do you see than a correct stack dump? Or have you tried doing a "bt" in insight's console? Is the stackdump there correct than? Roland