Search the FAQ Archives

3 - A - B - C - D - E - F - G - H - I - J - K - L - M
N - O - P - Q - R - S - T - U - V - W - X - Y - Z - Internet FAQ Archives

SGI apps Frequently Asked Questions (FAQ)
Section - -52- What's wrong with strip(1)?

( Single Page )
[ Usenet FAQs | Web FAQs | Documents | RFC Index | Restaurant inspections ]

Top Document: SGI apps Frequently Asked Questions (FAQ)
Previous Document: -51- Why does make(1) complain about syntax errors that I can't find?
Next Document: -53- Why does my floating point signal processing routine, when given certain inputs, run incredibly slowly and
See reader questions & answers on this topic! - Help others by sharing your knowledge

  In IRIX 5.2 and 5.3, strip(1) fails to remove all of the debugging
  information that it could. This isn't a big problem; it just wastes
  a bit of disk space. Patches 247 and 248 fix that bug.

  Patch 410 to IRIX 5.3 includes a new loader (ld32), the output of
  which strip mangles horribly. Patch 1068 and IRIX 6.2 include a strip
  which can strip ld32 binaries, but which does not follow symlinks.

  In IRIX 6.0 and 6.0.1, 'strip *' strips the first executable correctly
  and corrupts the rest. Work around the bug by stripping only one file
  at a time.

User Contributions:

Comment about this article, ask questions, or add new information about this topic: