This is the mail archive of the
insight-prs@sources.redhat.com
mailing list for the Insight project.
insight/45: Error message doesn't print when gdbtcl directory isn't found
- To: insight-gnats at sourceware dot cygnus dot com
- Subject: insight/45: Error message doesn't print when gdbtcl directory isn't found
- From: loewenhw at mbnet dot mb dot ca
- Date: 31 Aug 2000 16:19:29 -0000
- Reply-To: loewenhw at mbnet dot mb dot ca
- Resent-Cc: insight-prs at sourceware dot cygnus dot com
- Resent-Reply-To: insight-gnats@sourceware.cygnus.com, loewenhw@mbnet.mb.ca
>Number: 45
>Category: insight
>Synopsis: Error message doesn't print when gdbtcl directory isn't found
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Thu Aug 31 09:23:01 PDT 2000
>Closed-Date:
>Last-Modified:
>Originator: Howard Loewen
>Release: unknown-1.0
>Organization:
>Environment:
Windows 98 latest Cygwin
>Description:
After building insight with some BDM patches, attempts to execute GDB failed. The screen would display briefly and then dissapear. After debugging insight (with insight - the original version) I discovered a very nice error message burried in the code informing me that insight couldn't find the directory gdbtcl. This message was not displayed anywhere. After moving this directory to a location identified by the error message as acceptable I was able to run insight.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: