From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7072 invoked by alias); 9 Jul 2010 18:53:24 -0000 Received: (qmail 7064 invoked by uid 22791); 9 Jul 2010 18:53:24 -0000 X-SWARE-Spam-Status: No, hits=-5.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 09 Jul 2010 18:53:20 +0000 Received: from int-mx05.intmail.prod.int.phx2.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.18]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id o69IrHuk031879 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 9 Jul 2010 14:53:17 -0400 Received: from valrhona.uglyboxes.com (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx05.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id o69IrFmY031801 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 9 Jul 2010 14:53:16 -0400 Message-ID: <4C37701B.2020907@redhat.com> Date: Fri, 09 Jul 2010 18:53:00 -0000 From: Keith Seitz User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100430 Fedora/3.0.4-2.fc12 Lightning/1.0b2pre Thunderbird/3.0.4 MIME-Version: 1.0 To: George Najarian CC: insight@sourceware.org Subject: Re: CVS Insight running on Windows 7 x64 using ActiveTCL, mingw/msys, built for arm-none-eabi References: <4C376D11.9080604@najay.com> In-Reply-To: <4C376D11.9080604@najay.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes 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: 2010-q3/txt/msg00011.txt.bz2 On 07/09/2010 11:40 AM, George Najarian wrote: > What do I do to get the debug symbols included? If you need to debug Tcl code, there is some stuff in the sources to allow this, but I've never used it, and I don't know if it works at all. I usually do this the old-fashioned "printf"-like way. > Does Insight have a built in TCL prompt or trace window? Yes. See the README for details. I usually use either GDBTK_DEBUGFILE or GDBTK_DEBUG. I've not tried/used GDBTK_TRACE. YMMV. You can access the Tcl interpreter using the console command "tk". You can open a debug window after you start insight (i.e. GDBTK_DEBUG = 0) by typing at the console: (gdb) tk ManagedWin::open DebugWin Errors will show up in orange with "E", Info messages are green with "I", and warnings will be yellow (I think) with "W". I seem to recall fixing some target settings dialog issues before... What does "show version" display? My guess is this has something to do with the way COM ports are probed. That's what it was last time, as I recall. Keith