Da Zheng, le Tue 15 Dec 2009 23:16:11 +0800, a écrit : > > That could be a glitch of some other mechanism. You can use disassemble > > 0x01060089 to check what's really there and l * 0x01060089 to check > > which precise file that comes from. > disassemble is really useful:-) I really need to learn more about gdb. > I do see that evc_wait is called by mach_msg, but I cannot see evc_wait is > called either by any functions in glibc or by any in the build tree. > but 'l * 0x01060089' shows me no source file for the address. I think it's > because mach_msg is in the c library which doesn't have any debugging > information.
Use symbol-file /usr/lib/debug/lib/libc-2.10.2.so to load the debugging symbols. Samuel
