Date: Thu, 13 Aug 1998 10:50:51 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Al Christians <achrist AT easystreet DOT com>
cc: djgpp AT delorie DOT com
Subject: Re: Template/STL questions
In-Reply-To: <35D24762.7E27@easystreet.com>
Message-ID: <Pine.SUN.3.91.980813105025.2812J-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Wed, 12 Aug 1998, Al Christians wrote:

> I'm having trouble with a big program failing with little dignity and
> a segment fault, and am fishing for any ideas about what might be
> breaking it.

Since when bugs are solved by fishing? ;-)

Seriously, though: why don't you try the methodical way of debugging?
Did you try it and it failed?  If so, please describe how the usual
debugging failed, and you will get more efficient help.

But assuming you did NOT try the normal debugging way, here's what you
should do:

       1) Convert the stack dump printed when the program crashes to a
          human-readable description using `symify' (see section 9.2
          of the DJGPP FAQ list for details).

       2) Run the program under a debugger, put a breakpoint at the
          point where it crashes, and try to see what goes wrong here
          (SIGSEGV usually means a bad pointer, so look for these
          first).

If the above doesn't help, post more info (at least the symified crash
dump).