public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: "Timothy M. Shead" <tshead@k-3d.com>
To: egcs@cygnus.com
Cc: sourcenav@sourceware.cygnus.com
Subject: Re: Windows NT Failing on XRef Generation.
Date: Fri, 09 Feb 2001 12:27:00 -0000	[thread overview]
Message-ID: <3A845431.4010802@k-3d.com> (raw)
In-Reply-To: <Pine.SOL.3.91.1010209113324.22410F-100000@cse.cygnus.com>

Folks:

Let's bring this thing back down to Earth.  The bottom line, Lenny, is 
that a stack trace, Dr. Watson error, or core dump almost never provides 
enough information to debug a program.  Knowing the point at which a 
program stops running is less-than-half the problem - the context of 
what led up to that point is what developers need in order to find an 
answer.  In response to a bug report, any support organization, 
paid-or-unpaid, proprietary-or-free, is going to ask for a simple test 
case that is known-bad, so that the developers can repeat the problem 
and fix it.  Mo's request for a set of sample input data that causes the 
parser to crash would not be considered unusual by any of the support 
organizations that I've ever worked for (all of which have been 
proprietary, for-profit companies).

Regards,
Timothy M. Shead

  reply	other threads:[~2001-02-09 12:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-09  8:36 Story, Lenny
2001-02-09  9:57 ` Berek
2001-02-09 10:45   ` Kenneth Luke
2001-02-09 12:01 ` Mo DeJong
2001-02-09 12:27   ` Timothy M. Shead [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-02-09 18:29 Story, Lenny
2001-02-09 11:41 Story, Lenny
2001-02-08 20:16 Story, Lenny
2001-02-08 20:29 ` Mo DeJong
2001-02-08 20:16 Story, Lenny
2001-02-08 16:15 Story, Lenny
2001-02-08 12:14 Story, Lenny
2001-02-08 12:25 ` Ian Roxborough
2001-02-08  9:52 dave.banham
2001-02-08  9:05 Story, Lenny
2001-02-08  9:55 ` Syd Polk
2001-02-08 11:25 ` Berek

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=3A845431.4010802@k-3d.com \
    --to=tshead@k-3d.com \
    --cc=egcs@cygnus.com \
    --cc=sourcenav@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).