From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,8c54bb73b6fd8d22
X-Google-Attributes: gid103376,public
From: kenner@lab.ultra.nyu.edu (Richard Kenner)
Subject: Re: GDB Woes Continued: language related ?
Date: 1998/02/10
Message-ID: <6bocee$lql$1@news.nyu.edu>#1/1
X-Deja-AN: 323607367
References: <dewar.886646918@merv> <01bd333c$4fb8b000$452c5c8b@aptiva>
 <rracine-0902980655220001@rjr1287.draper.com>
X-Complaints-To: usenet@news.nyu.edu
X-Trace: news.nyu.edu 887076110 22357 (None) 128.122.140.194
Organization: New York University Ultracomputer Research Lab
Newsgroups: comp.lang.ada
Date: 1998-02-10T00:00:00+00:00
List-Id: <comp.lang.ada>


In article <rracine-0902980655220001@rjr1287.draper.com> rracine@draper.com (Roger Racine) writes:
>Yes, but I have what I am told is a rare version: Windows 3.1 => Windows
>95 Upgrade that I bought in a store.  This version is supposedly fraught
>with peril for gdb.

Download and install the "Service release 1" and some of its bugfixes
from Microsoft and install.  That's a worthwhile thing to do anyway
and I've run GDB on such a system with no problem.

BTW, the problem isn't GDB per se, but the Borland C runtime that is
used by the TK and TCL DLLs that it uses.