From: Thomas Demmer Newsgroups: comp.os.msdos.djgpp Subject: strip.exe and -gstabs broken Date: Wed, 15 Apr 1998 19:23:28 +0200 Organization: Lehrstuhl fuer Stroemungsmechanik Lines: 38 Message-ID: <3534ED10.4AD5DF9B@LSTM.Ruhr-UNI-Bochum.De> NNTP-Posting-Host: bvb.lstm.ruhr-uni-bochum.de Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Precedence: bulk Hi, SET has a patched version of gcc 2.7.2.1 on his homepage that supports the stabs debugging info format. Compiling C++ code with -gstabs allows some nice debugging possibilities that the usual -g does not. However, running strip.exe on the executable seems to ruin the image, I guess already the startup code. The only thing you get is a "General Protection Fault", nothing else. The message is: General Protection Fault at eip=123a flags=3246 and some registers... No stack traceback, so I guess strip screws up the image quite completely. (Trivial) C code seems not to be affected, although I didn't try a more complicated source. Eli proposed to use -gxcoff instead, but that only gets you a warning "debugging format not supported by this version of gcc". I am not sure if 2.8 supports stabs, but I guess that if so, strip.exe will ruin those images, too. The only way around this, so far, is to rebuild all without debugging info... -- Ciao Tom ************************************************************* * Thomas Demmer * * Lehrstuhl fuer Stroemungsmechanik * * Ruhr-Uni-Bochum * * Universitaetsstr. 150 * * D-44780 Bochum * * Tel: +49 234 700 6434 * * Fax: +49 234 709 4162 * * http://www.lstm.ruhr-uni-bochum.de/~demmer * *************************************************************