On 07/11/2011 08:00 AM, Naveen Kumar wrote: >>>> objdump --dwarf /lib/ld-2.2.4.so > > John looks like the version of objdump that came with the system does not > have the --dwarf option. It has a -G(--stabs) for STABS info. Would that be > sufficient ?
OK, this is older software. (It's always a good idea to specify explicitly the version of OS, compiler, runtime libraries.) Use whatever option will turn the debuginfo into human-readable form; probably --stabs will work. > >>>The C run-time library and the operating system itself also are acting >>>unfriendly. The OS should implement the concept of __NR_exit_group. >>>If the OS does not, then the C run-time library should emulate it >>>(if nothing else, by aliasing exit_group() to exit().) Consider >>>asking your OS and C run-time library for such implementations. > Couldnt valgrind be changed to add a __NR_exit after __NR_exit_group. ? That > way on newer OSes the exit_group would take care of exiting and code would > never reach __NR_exit. On older systems the __NR_exit_group would be ignored > and __NR_exit would come into the picture. Yes, this is one possibility, and it might be the shortest or easiest right now. But the other players (OS, C runtime library) should be requested to behave better, too. -- ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
