From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15920 invoked by alias); 17 Sep 2008 15:04:48 -0000 Received: (qmail 15906 invoked by uid 22791); 17 Sep 2008 15:04:47 -0000 X-Spam-Check-By: sourceware.org Received: from vms173001pub.verizon.net (HELO vms173001pub.verizon.net) (206.46.173.1) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 17 Sep 2008 15:04:08 +0000 Received: from [10.10.1.168] ([209.190.166.162]) by vms173001.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0K7C00769HRP74U3@vms173001.mailsrvcs.net> for insight@sourceware.org; Wed, 17 Sep 2008 10:02:13 -0500 (CDT) Date: Thu, 18 Sep 2008 22:11:00 -0000 From: John Fine Subject: Re: Can't debug x86_64 C++ programs. In-reply-to: <48D0A482.8060000@redhat.com> To: Keith Seitz Cc: insight@sourceware.org Message-id: <48D11BED.20906@verizon.net> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7bit References: <48D024D1.3000107@verizon.net> <48D0A482.8060000@redhat.com> User-Agent: Thunderbird 2.0.0.16 (Windows/20080708) 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: 2008-q3/txt/msg00064.txt.bz2 Keith Seitz wrote: > >> If I try to view the registers window anytime after pressing Run, the >> whole debugger crashes. If I view the register window first, it >> appears, then when I press run it populates, then a moment later the >> whole debugger crashes. > > Once again, I am sorry, but I cannot reproduce this (on x86). > I got the core file, then used gdb to get a backtrace. The beginning of that is #0 get_register (regnum=2, arg=) at ../../insight-6.8/gdb/gdbtk/generic/gdbtk-register.c:331 #1 0x00000000004addd8 in gdb_register_info (clientData=, interp=0xa93ab0, objc=, objv=0xa96148) at ../../insight-6.8/gdb/gdbtk/generic/gdbtk-register.c:426 #2 0x00000000004a8ff7 in wrapped_call (opaque_args=0x7fbfff5cf0) at ../../insight-6.8/gdb/gdbtk/generic/gdbtk-cmds.c:423 #3 0x0000000000505f3b in catch_errors (func=0x4a8fe0 , func_args=0x7fbfff5cf0, errstring=0x77ecc2 "", mask=) at ../../insight-6.8/gdb/exceptions.c:513 #4 0x00000000004a8ecb in gdbtk_call_wrapper (clientData=0x4adb90, interp=0xa93ab0, objc=3, objv=0xa96138) at ../../insight-6.8/gdb/gdbtk/generic/gdbtk-cmds.c:354 #5 0x00000000007069b1 in TclEvalObjvInternal (interp=0xa93ab0, objc=3, objv=0xa96138, command=0x0, length=0, flags=0) at ../../../insight-6.8/tcl/unix/../generic/tclBasic.c:3048 #6 0x000000000072a414 in TclExecuteByteCode (interp=0xa93ab0, codePtr=0x196f350) at ../../../insight-6.8/tcl/unix/../generic/tclExecute.c:1431 #7 0x000000000072d548 in TclCompEvalObj (interp=0xa93ab0, objPtr=0x16559e0) at ../../../insight-6.8/tcl/unix/../generic/tclExecute.c:1008 #8 0x00000000007089e7 in Tcl_EvalObjEx (interp=0x3e30031640, objPtr=0x51, flags=0) at ../../../insight-6.8/tcl/unix/../generic/tclBasic.c:3944 #9 0x0000000000669f41 in Itcl_EvalMemberCode (interp=0xa93ab0, mfunc=0x16d6b40, member=0x16d6b70, contextObj=0x16d0f20, objc=2, objv=0xa96128) at /home/fine/insight-6.8/itcl/itcl/generic/itcl_methods.c:1003 #10 0x000000000066a9e6 in Itcl_ExecMethod (clientData=, interp=0xa93ab0, objc=2, objv=0xa96128) at /home/fine/insight-6.8/itcl/itcl/generic/itcl_methods.c:1516 #11 0x00000000007069b1 in TclEvalObjvInternal (interp=0xa93ab0, objc=2, objv=0xa96128, command=0x0, length=0, flags=0) at ../../../insight-6.8/tcl/unix/../generic/tclBasic.c:3048 #12 0x000000000072a414 in TclExecuteByteCode (interp=0xa93ab0, codePtr=0x197c8a0) at ../../../insight-6.8/tcl/unix/../generic/tclExecute.c:1431 I'll try to dig into gdbtk-register.c myself and see if I can understand the problem. But meanwhile, I thought the backtrace might help you tell me what to look for.