From: Hans-Bernhard Broeker Newsgroups: comp.os.msdos.djgpp Subject: Re: Strange behavior of compiler. Date: 29 Jun 2001 10:28:04 GMT Organization: Aachen University of Technology (RWTH) Lines: 17 Message-ID: <9hhl7k$qdd$1@nets3.rz.RWTH-Aachen.DE> References: <3b3b4af5 DOT 212572777 AT news DOT primus DOT ca> <4331-Thu28Jun2001221650+0300-eliz AT is DOT elta DOT co DOT il> <3b3bea8a DOT 253431390 AT news DOT primus DOT ca> NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de X-Trace: nets3.rz.RWTH-Aachen.DE 993810484 27053 137.226.32.75 (29 Jun 2001 10:28:04 GMT) X-Complaints-To: abuse AT rwth-aachen DOT de NNTP-Posting-Date: 29 Jun 2001 10:28:04 GMT Originator: broeker@ To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Graaagh the Mighty wrote: [...] > Okay, so where in this picture does the stabs format and some problem > or conflict between it and the available space in COFF images fit? COFF's own type of debugging info has some internal limitations, and stabs *removes* those limitations. Whatever that discussion was, you remembered the advice the wrong way round: for debugging C++ apps with inlined methods, and for large code (more than 64K lines of code with debug info in them), you should by all means use -gstabs+ or -ggdb instead of plain -g. But sometimes, even stabs isn't enough, and that's why we're now moving towards DWARF2. -- Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de) Even if all the snow were burnt, ashes would remain.