Using NM, you can generate a link map sorted in lots of different ways, including different types of information. How useful this is in troubleshooting a problem that someone else gave is limited. About the only thing you can really do is to figure out the function you are in. If you are ambitious, what you can do is have the SIGSEGV generate core. Assuming you have an identical version of the binary (and the source that generated it) at your site, the user can send you the core file and you can then use GDB on it to look at stack, variables, etc. Dave -----Original Message----- From: Robin Rowe [mailto:rower@xxxxxxxxxxxxxxx] Sent: Monday, September 29, 2003 11:02 PM To: gcc-help@xxxxxxxxxxx Subject: What good is crash instruction pointer? Hi. I want my apps to keep a crash log that users can send in with bug reports. I can use sigaction to catch the instruction pointer on SIGSEGV. My question is can I do anything useful with that pointer address if a user emails it to me? Is there a map file I can generate that will tell me where in the source code that pointer corresponds, what line of code the program choked on? Thanks! Robin --------------------------------------------------------------------------- Robin.Rowe@xxxxxxxxxxxxxxx Hollywood, California www.CinePaint.org Free motion picture and still image editing software
