public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: CBFalconer <cbfalconer@yahoo.com>
To: cygwin@cygwin.com
Subject: Re: gdb hangs on a 486
Date: Thu, 31 Oct 2002 09:31:00 -0000	[thread overview]
Message-ID: <3DC1585D.37B864D@yahoo.com> (raw)
In-Reply-To: <4.3.1.2.20021031083212.017487d8@pop.rcn.com>

"Larry Hall (RFK Partners, Inc)" wrote:
> 
> At 11:13 PM 10/30/2002, CBFalconer wrote:
> >I have been trying out gdb in Cygwin, and found it to hang and/or
> >crash under W98, running on a 486.  The output of gdb --version
> >is:
> >
... snip ...
> > > This GDB was configured as "i686-pc-cygwin".
> >                               ^^^^^^^^^^^^^^
> >This appears unwarranted.  I would have assumed gdb would test and
> >adapt itself to the processor on which it is running.
> 
> At this point, I think most (all?) Cygwin packages are configured
> like this. Whether or not that's true, it's not unwarranted. There's 
> good reason to make use of the newer architectures' capabilities.

I can easily believe that.  It seems very poor practice to make
these assumptions without checking them somewhere and generating a
warning.  Such things can go in initialization or loading code.

... snip ...
> 
> gdb -nw
> 

Are you saying that the problem is limited to the GUI interface? 
Is this known, or just a guess?

> 
> Sounds like you may want to get the source, reconfigure, and build
> your own version targeting i386 or i486.

A non-trivial job, especially if the very tools are suspect.

-- 
Chuck F (cbfalconer@yahoo.com) (cbfalconer@worldnet.att.net)
   Available for consulting/temporary embedded and systems.
   <http://cbfalconer.home.att.net>  USE worldnet address!



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  reply	other threads:[~2002-10-31 16:52 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-31  2:23 CBFalconer
2002-10-31  6:36 ` Larry Hall (RFK Partners, Inc)
2002-10-31  9:31   ` CBFalconer [this message]
2002-10-31 11:54   ` Christopher Faylor
2002-10-31 22:23     ` CBFalconer
2002-10-31 23:40       ` Christopher Faylor
     [not found]         ` <3DC1F0A0.D1E3388E@yahoo.com>
2002-11-01  6:44           ` Christopher Faylor
2002-10-31 22:39     ` CBFalconer
2002-11-01  7:47 ` J. David Bryan
2002-10-31  8:25 Scott Prive
2002-10-31  9:57 lhall
2002-10-31 10:30 lhall
2002-10-31 11:31 ` Randall R Schulz
2002-10-31 11:44 Scott Prive
2002-10-31 12:22 lhall
2002-10-31 14:57 Scott Prive
2002-10-31 15:02 ` Christopher Faylor
2002-11-01  9:35 lhall
2002-11-01 12:42 ` CBFalconer

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=3DC1585D.37B864D@yahoo.com \
    --to=cbfalconer@yahoo.com \
    --cc=cbfalconer@worldnet.att.net \
    --cc=cygwin@cygwin.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).