[2186] in SIPB_Linux_Development
Re: Official policy on what build flags to use for the release?
daemon@ATHENA.MIT.EDU (Derek Atkins)
Thu Oct 1 08:54:52 1998
To: Salvatore Valente <svalente@MIT.EDU>
Cc: ghudson@MIT.EDU, tytso@MIT.EDU, linux-dev@MIT.EDU
From: Derek Atkins <warlord@MIT.EDU>
Date: 01 Oct 1998 08:49:37 -0400
In-Reply-To: Salvatore Valente's message of Wed, 30 Sep 1998 17:56:35 -0400
The only problem is that your "future build" might not match the build
on the packs, so you might not be able to debug it (and the core dump,
if any, will be useless). If you compile -g originally, and put a
stripped version on the packs (saving the unstripped version in the
build tree) then you can just debug in the build tree directly without
rebuilding anything, and core dumps will work.
-derek
Salvatore Valente <svalente@MIT.EDU> writes:
>
>
> The thing I'm not sure about is:
>
> If someone sends in a bug report that says "This program crashes when
> I press the 'a' key," I can build a copy of the program with -g and
> try to debug it. So, if the person who originally noticed the bug has
> no interest in debugging it, does it make a difference if the program
> he was running was built with -g? (Specifically, does a program
> generate a more meaningful core dump if it was built with -g?)
>
> Thanks,
> Sal.
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
warlord@MIT.EDU PGP key available
