public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Charles Duffy <cduffy@bigfoot.com>
To: insight@sourceware.cygnus.com
Subject: 19991011 snapshot bug displaying asm (cross-debugging)
Date: Sun, 17 Oct 1999 17:11:00 -0000	[thread overview]
Message-ID: <19991017171829.A21217@cduffy.csuchico.edu> (raw)

First off, sorry 'bout sending this to you rather than the list (or
creating a problem report). My home machine (which I'm using for this)
is rather connectivity-challenged at the moment, largely limiting me
to email. (Actually, these are political rather than technical
limitations... but that's another discussion).

If you'd be so kind as to forward this wherever it would do the most
good (one of the mailing lists, perhaps?) or create an appropriate
entry in the bug-tracking database, I'd be appreciative.

Thanks! (Btw, I don't mind helping to debug a bit of C code, but this
TCL-based stuff is a bit different than what I'm used to. If you can
track the problem to something in C, I wouldn't mind trying to throw a
few hours at it).

---

Good day. I've done a bit of hacking at Insight, and (with the help of
some patches written for gdb 4.18 by others) am presently using it for
remote-debugging a PalmOS-based app. However, displaying MIXED mode
appears to hang (It's possible that there's just a lot going on over
the serial connection; I've not looked into this), and displaying ASM
or SRC+ASM mode results in a segfault in tclUtil.c while trying to
eval "namespace inscope ::SrcWin {::.srcwin0.srcwin mode}
.srcwin0.srcwin.container.pane3.childsite.con.mode ASSEMBLY; unset
::combobox::.srcwin0.srcwin.container.pane3.childsite.con.mode::widgets(after)"
as the interpreter tries to increase the reference count for an object
supposedly located at 0xe.

Requesting disassembly in the console, by contrast, works fine.

This does not occur when locally debugging a native target. I'm
uncertain as to whether it's the remote debugging or non-native target
which is causing this error.

If you want a full diff between my copy and the snapshot, just ask.

Thanks!
-- 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v0.9.9 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iEYEAREBAAYFAjgKZ1UACgkQ6i7haXNDg8IRygCgqWkpupE0SLyKB89irerMamqM
sKwAmwUqlq5klBsRVPvMSTaobm4wLbPZ
=4OHv
-----END PGP SIGNATURE-----

                 reply	other threads:[~1999-10-17 17:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=19991017171829.A21217@cduffy.csuchico.edu \
    --to=cduffy@bigfoot.com \
    --cc=insight@sourceware.cygnus.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).