public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: "Schumacher, Gordon" <gordon_schumacher@maxtor.com>
To: "'Keith Seitz'" <keiths@redhat.com>
Cc: "Insight list (E-mail)" <insight@sources.redhat.com>
Subject: RE: Building Insight snapshot on CygWin?
Date: Tue, 03 Jun 2003 20:02:00 -0000	[thread overview]
Message-ID: <E836CBDA0DC0D5118606009027DE2A0C983E50@mcoexc02.mlm.maxtor.com> (raw)

# From: Keith Seitz [mailto:keiths@redhat.com]
# Sent: Tuesday, May 27, 2003 12:36 PM
# To: Schumacher, Gordon
# Cc: Insight list (E-mail)
# Subject: RE: Building Insight snapshot on CygWin?
# 
# I don't see any of this. Does libtcl84.a not contain this symbol? What
# does "head config.status" say? Can you do a "make clean; make 
# > make.out
# 2>&1" and send make.out?

Sorry about the delay in replying; I was out for all of last week.

So, I tried snapshot 20030602, and that one builds fine (with dejagnu nuked)
even as a CygWin to i686-pc-msdosdjgpp cross-debugger.  But, now I've got
problems getting it to run properly...

About 90% of the time, option buttons and checkboxes don't change state upon
being clicked.  They highlight - but the check doesn't change.  Option
buttons usually contain *neither* setting.
I can connect to an application via Remote/Serial, but when it hits a
breakpoint, the main window says only "Select a function to disassemble".  I
can pick a source file, but I can't seem to get it to indicate where it is
stopped at (i.e., no "you are here" highlight.)  Single-stepping does
nothing; continue and "step asm" commands seem to do *something* but without
knowing where the PC is there's not much use to that.

Would it be helpful to try a Linux to DJGPP cross-debugger and see if that
works?  I'm not quite sure where to even start looking on this one...!

My cross-binutils package is version 2.13.2, FWIW.

             reply	other threads:[~2003-06-03 20:02 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-03 20:02 Schumacher, Gordon [this message]
2003-06-06 20:45 ` Keith Seitz
  -- strict thread matches above, loose matches on Subject: below --
2003-07-07 19:44 John Lowen
2003-07-07 19:57 ` Keith Seitz
2003-06-24  1:46 Kevin Powell
2003-06-24  2:00 ` Keith Seitz
2003-06-24  0:14 Kevin Powell
2003-06-24  1:09 ` Keith Seitz
2003-06-23 23:18 Kevin Powell
2003-06-23 23:31 ` Keith Seitz
2003-06-09 15:53 Schumacher, Gordon
2003-06-09 17:53 ` Keith Seitz
2003-06-09  9:28 vadraj kulkarni
2003-06-11 20:11 ` Keith Seitz
2003-05-21 20:47 Schumacher, Gordon
2003-05-27 18:30 ` Keith Seitz
2003-05-21 17:18 Schumacher, Gordon
2003-05-21 17:19 ` Keith Seitz
2003-05-21 18:55   ` Keith Seitz
2003-05-21 19:02     ` Martin M. Hunt
2003-05-21 21:37       ` Keith Seitz
2003-05-21 23:08         ` Keith Seitz
2003-05-21 23:49           ` Andrew Cagney
2003-05-21 16:54 Schumacher, Gordon
2003-05-21 17:02 ` Keith Seitz
2003-05-21 19:58 ` Martin M. Hunt

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=E836CBDA0DC0D5118606009027DE2A0C983E50@mcoexc02.mlm.maxtor.com \
    --to=gordon_schumacher@maxtor.com \
    --cc=insight@sources.redhat.com \
    --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).