Very Computer

by **Paul Nev** » Wed, 27 May 1992 20:56:24

A couple of days ago I asked if it's safe to "strip" binaries. I rec'd a lots
of responses, and I'd like to thank all of you. As of now, I'll stop
acknowledging answers individually, and please stop sending me letters on
this subject.

The Bottom Line: It's generally safe to strip (except the kernel) BUT
debugging will be (practivally) impossible later on. No gain in speed etc.
except in space.

Take care...Paul

P.O. Box 3341 1-(614)-292-3317 (Office)
Columbus, Ohio 43210-0341 1-(614)-292-5310 (Answering Machine)
The United States of America 1-(614)-459-5615 (FAX)

by **-*_Spikey_Tribble_** » Thu, 28 May 1992 04:04:09

> > The Bottom Line: It's generally safe to strip (except the kernel) BUT
> > debugging will be (practivally) impossible later on. No gain in speed etc.
> > except in space.

I'll get it right this time ... don't quit the editor before editing.

Debugging is impossible without symbol table info, but the whole idea of
such things is that once you've debugged, you strip it off because it's dead,
non-functional and unnecessarily space-consuming material (often 30-50% of
the size of an executable) -- you really ought to strip them before you put
them in your $HOME/bin/ ...

> --

> # Have you read your Book In Basic Life Education today ? You should !! #
> # Any views I express are not necessarily those of Brighton Polytechnic #
> ###################### "surivorter erutangis a ma I" ######################

--

# Have you read your Book In Basic Life Education today ? You should !! #
# Any views I express are not necessarily those of Brighton Polytechnic #
###################### "surivorter erutangis a ma I" ######################

by **-*_Spikey_Tribble_** » Thu, 28 May 1992 04:00:41

> A couple of days ago I asked if it's safe to "strip" binaries. I rec'd a lots
> of responses, and I'd like to thank all of you. As of now, I'll stop
> acknowledging answers individually, and please stop sending me letters on
> this subject.

> The Bottom Line: It's generally safe to strip (except the kernel) BUT
> debugging will be (practivally) impossible later on. No gain in speed etc.
> except in space.

> Take care...Paul

> P.O. Box 3341 1-(614)-292-3317 (Office)
> Columbus, Ohio 43210-0341 1-(614)-292-5310 (Answering Machine)
> The United States of America 1-(614)-459-5615 (FAX)

--

# Have you read your Book In Basic Life Education today ? You should !! #
# Any views I express are not necessarily those of Brighton Polytechnic #
###################### "surivorter erutangis a ma I" ######################

by **Matthew Farwe** » Fri, 29 May 1992 00:14:35

>> > The Bottom Line: It's generally safe to strip (except the kernel) BUT
>> > debugging will be (practivally) impossible later on. No gain in speed etc.
>> > except in space.
> I'll get it right this time ... don't quit the editor before editing.

Learn how to cancel articles as well.

Quote:> Debugging is impossible without symbol table info, but the whole idea of
>such things is that once you've debugged, you strip it off because it's dead,
>non-functional and unnecessarily space-consuming material (often 30-50% of
>the size of an executable) -- you really ought to strip them before you put
>them in your $HOME/bin/ ...

Not impossible. You could:

1) Have a good debugging technique. A printf every second line is the
easy way to do this. Stripping won't get rid of this information.
2) Use adb.

Dylan.
--
It is no coincidence that in no known language does the phrase 'As
pretty as an Airport' appear -- Douglas Adams

by **Brian Fitzgera** » Fri, 29 May 1992 01:38:54

>The Bottom Line: It's generally safe to strip (except the kernel) BUT

You might not want to strip an executable that does its own dynamic loading.
One commercial package I know of warns you not to.

Brian

by **Duncan Sincla** » Fri, 29 May 1992 05:03:09

Quote:>> Debugging is impossible without symbol table info, but the whole idea of
>>such things is that once you've debugged, you strip it off because it's dead,
>>non-functional and unnecessarily space-consuming material (often 30-50% of
>>the size of an executable) -- you really ought to strip them before you put
>>them in your $HOME/bin/ ...
>Not impossible. You could:
>1) Have a good debugging technique. A printf every second line is the
>easy way to do this. Stripping won't get rid of this information.
>2) Use adb.

3) I once saw a program that claimed to be able to partially re-build the
symbol table from the information used for binding shared libraries in
SunOS 4.*. Of course it wasn't able to recover labels of local/"static"
functions, etc. but it's still better than a poke in the eye with a wet fish.

--

University of Glasgow |..!mcsun!ukc!uk.ac.glasgow.dcs!sinclair
--- Rave Culture: Don't techno for an answer. ---

by **-*_Spikey_Tribble_** » Sat, 30 May 1992 21:14:59

> >> Debugging is impossible without symbol table info ...
> >2) Use adb.
> [...]
> 3) I once saw a program that claimed to be able to partially re-build the
> symbol table from the information used for binding shared libraries in
> SunOS 4.*. Of course it wasn't able to recover labels of local/"static"
> functions, etc. but it's still better than a poke in the eye with a wet fish.

Any idea where it was ? I was actually trying to fiddle with the reloc info
recently but it's a bit complex -- at least it is given the small amount of
time I can spare for such things at the moment.
--

# Have you read your Book In Basic Life Education today ? You should !! #
# Any views I express are not necessarily those of Brighton Polytechnic #
###################### "surivorter erutangis a ma I" ######################

by **Nivas Madh** » Tue, 02 Jun 1992 23:00:27

> >> Debugging is impossible without symbol table info ...
> >2) Use adb.

Any suggestions how to debug if you just have a core dump from
a stripped executable? I know how to get a backtrace if the executable
is not stripped (using adb) but am totally lost if someone gives a
core and an exectable - I just cannot get any info out of the dump.
adb keeps on saying "text address not found".

Thanks for any info,

nivas
......................................................................

1101 E. University Av Urbana IL 61801 Ma bell (217) 384 8588

by **Marty Leisner 311/?** » Tue, 09 Jun 1992 23:32:27

I tend to think things should not be stripped (if you have space, and space is awfully cheap).

If its not stripped and the source is on-line, whenever a bug appears, it is relatively
easy to fire up the de*.

--
marty

Member of the League for Programming Freedom

Very Computer

Thanks for info on "stripping"

Thanks for info on "stripping"

Thanks for info on "stripping"

Thanks for info on "stripping"

Thanks for info on "stripping"

Thanks for info on "stripping"

Thanks for info on "stripping"

Thanks for info on "stripping"

Thanks for info on "stripping"

Thanks for info on "stripping"