On Thu, Nov 18, 2010 at 11:20:02PM -0800, sureshsoft wrote:
> "Once you use this command, symbolic debugging of the file is difficult;
> therefore, you should normally use the strip command only on production
> modules that you have debugged and tested." By this what i understood is
> strip doesn't
I want to use gdb to do that.. In gdb we can load release version of
executable's symbol file using symbol-file . when we do
that, the debug information is gets attached in the debugging session and we
can see all debug information like line numbers, functions names as we see
with a debug binary.
> I was trying to use the objcopy with following arguments to copy the debug
> information to another file..
> bash-3.2#./objcopy --only-keep-debug testvolumeinfocollector
> testvolumeinfocollector.dbg
> BFD: testvolumeinfocollector: Unrecognized storage class 0 for *ABS* symbol
> `volumeinfocollec
