public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: John Fine <johnsfine@verizon.net>
To: Keith Seitz <keiths@redhat.com>
Cc: insight@sourceware.org
Subject: Re: Can't debug x86_64 C++ programs.
Date: Thu, 18 Sep 2008 22:11:00 -0000	[thread overview]
Message-ID: <48D11BED.20906@verizon.net> (raw)
In-Reply-To: <48D0A482.8060000@redhat.com>

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=<value optimized out>)
    at ../../insight-6.8/gdb/gdbtk/generic/gdbtk-register.c:331
#1  0x00000000004addd8 in gdb_register_info (clientData=<value optimized 
out>, interp=0xa93ab0,
    objc=<value optimized out>, 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 <wrapped_call>, 
func_args=0x7fbfff5cf0,
    errstring=0x77ecc2 "", mask=<value optimized out>) 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=<value optimized 
out>, 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.

  parent reply	other threads:[~2008-09-17 15:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-18 20:53 John Fine
2008-09-18 21:19 ` Keith Seitz
2008-09-18 21:37   ` John Fine
2008-09-19  7:26     ` Keith Seitz
2008-09-19 14:27       ` John Fine
2008-09-19 18:47         ` Keith Seitz
2008-09-18 22:11   ` John Fine [this message]
2008-09-18 22:27   ` John Fine
2008-09-18 23:04     ` Keith Seitz
2008-09-18 23:25       ` John Fine
2008-09-19  8:20         ` Keith Seitz
2008-09-19 13:27           ` John Fine
2008-09-19 16:38             ` Keith Seitz
2008-09-20 21:22               ` John Fine
2008-09-22 18:35                 ` John Fine
2008-09-19  2:17 ` Keith Seitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48D11BED.20906@verizon.net \
    --to=johnsfine@verizon.net \
    --cc=insight@sourceware.org \
    --cc=keiths@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).