John Fine wrote: > Any suggestions on diagnosing or correcting this problem? How can I > tell if the problem is in the .so file or in the tools I've tried for > looking at the .so file. The first thing to check is whether the .so actually contains debug info, since it sounds like it has been inadvertently stripped. You can check by running objdump -wh and verifying that it contains the .debug_* sections. If it doesn't then something in your build system is causing the debug info to be omitted, e.g. -s in LDFLAGS. If that doesn't explain it, then you need to provide a standalone testcase that reproduces the problem. Or at least show us the exact list of commands used to compile and link. I can't think of anything that changed between gcc 4.1 and 4.3 that would cause this, nor should the binutils version matter that much (as long as it's not an ancient version.) I just checked on an old debian system and binutils 2.15 had no problem displaying line number info in a .so generated by gcc 4.4. Brian
