Date: Mon, 1 Nov 1999 13:53:42 +0200 (IST) From: Eli Zaretskii X-Sender: eliz AT is To: Marty Leisner cc: djgpp-workers AT delorie DOT com Subject: Re: -g vs -s In-Reply-To: <199910312122.QAA01510@rochester.rr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Reply-To: djgpp-workers AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Sun, 31 Oct 1999, Marty Leisner wrote: > When you give -g, you can get line number/parameters in the core dump. > > When you do nothing, you get minimal information (i.e. the stack backtrace, > no parameters). But you still can get the same info as with -g if you later recompile with -g and *then* debug the core file, right? That's exactly what happens with DJGPP-style traceback: you can't get line numbers info if the binary was stripped, but if you save the traceback and rebuild with -g, you can have the line numbers info. That's why I think that lack of core files shouldn't matter in this case: the effect of having a stripped binary on the traceback and on the core file is similar. > I haven't used djgpp in several years, if symify is the equavilent to reading > the stack on a core dump, by all means make it the default behavior... SYMIFY reads the stack frame traceback from the video memory (or, under a special option, from a file), and then adds source file name and line number information to it. For this to work, the binary needs to be unstripped.