public inbox for insight-prs@sourceware.org
help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: kseitz@sources.redhat.com
Cc: insight-prs@sources.redhat.com,
Subject: Re: insight/276: Insight blows up the term when run
Date: Sat, 19 Nov 2005 16:53:00 -0000	[thread overview]
Message-ID: <20051119165301.30707.qmail@sourceware.org> (raw)

The following reply was made to PR insight/276; it has been noted by GNATS.

From: Keith Seitz <keiths@redhat.com>
To: freddie@sb.net, insight-gnats@sources.redhat.com,
        insight-prs@sources.redhat.com
Cc:  
Subject: Re: insight/276: Insight blows up the term when run
Date: Sat, 19 Nov 2005 08:50:33 -0800

 http://sourceware.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=insight&pr=276
 
 Program received signal EXC_BAD_ACCESS, Could not access memory.
   Reason: KERN_PROTECTION_FAILURE at address: 0x00000064
   0x9b51bd24 in Tcl_GlobalEval ()
   (gdb) backtrace
   #0  0x9b51bd24 in Tcl_GlobalEval ()
   #1  0x000175f8 in gdbtk_source_start_file () at .././gdb/gdbtk/
   generic/gdbtk.c:620
 
 Couple of things...
 
 In frame #1 (gdbtk_source_start_file, gdbtk.c:620), what exactly is 
 0x64, "gdbtk_interp" or "script"?
 
 Instead of build gdb/insight, if you just built tcl and tk, do tclsh and 
 wish run? Can you run the tk demos (in src/tk/library/demos)?
 
 I suspect that our version tcl and tk don't work on OS X. In fact, this 
 is the first I've heard of anyone trying to even run Insight on OS X!
 
 Keith


             reply	other threads:[~2005-11-19 16:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-19 16:53 Keith Seitz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-11-16  4:53 Kingston Co.
2005-11-11 17:41 kseitz

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=20051119165301.30707.qmail@sourceware.org \
    --to=keiths@redhat.com \
    --cc=insight-prs@sources.redhat.com \
    --cc=kseitz@sources.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).