[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Automatic debug symbol generation
From: |
Bob Rossi |
Subject: |
Re: Automatic debug symbol generation |
Date: |
Thu, 23 Apr 2009 11:30:58 -0400 |
User-agent: |
Mutt/1.5.17+20080114 (2008-01-14) |
On Thu, Apr 23, 2009 at 05:08:16PM +0200, Jan Engelhardt wrote:
>
> On Thursday 2009-04-23 14:51, Bob Rossi wrote:
> >
> >>> What's the advantage over just installing binaries into $(bindir)
> >>> without stripping them? **Non-brain-damaged** systems won't
> >>> load them from the file anyway for normal execution.
>
> [emphasis added by me]
>
> >On mingw/msys the executables with debug grow to be huge (10x the size).
> >Before stripping, my bin dir is 920 megs. After stripping it's 72 megs.
> >The mere size of the executables cause **windows** to load them rather slow.
> >If you have to start a program many times, as I do, it's noticable.
>
> But yeah, even if this seems like a case of brain-damage,
> this is _the_ argument for me to support having this make target.
I'm finding that if I do something like this,
install-exec-hook:
for prog in foo bar; do \
objcopy --only-keep-debug $prog.exe $prog.dbg; \
objcopy --strip-debug $prog.exe; \
objcopy --add-gnu-debuglink=$prog.dbg $prog.exe; \
done
it takes so much longer to do the install rule, which causes me
to not really save any time....to bad.
Bob Rossi
- Automatic debug symbol generation, JRS, 2009/04/22
- Re: Automatic debug symbol generation, Ralf Wildenhues, 2009/04/25
- Re: Automatic debug symbol generation, JRS, 2009/04/25
- Re: Automatic debug symbol generation, Ralf Wildenhues, 2009/04/27
- Re: Automatic debug symbol generation, JRS, 2009/04/27
- Re: Automatic debug symbol generation, Philipp Thomas, 2009/04/28