Re: why i cant find function names in stack trace with gdb e2point@ wrote: >igot acore dump from the customer which was created using arelease >binary (without debugging symbols). when ianalyzed itusing gdb with >the binary which has debug symbols, itjust show function addresses as >follows. why doesn't itshow more details? >Thread 25(process 5939): >#00xffffe405 in__kernel_vsyscall () >#10x00129f6e in??() >#20xf78ec2ac in??() >#30x001203aa in??() >#40xf78ee0e0 in??() >#50x00000002 in??() >#60x00120382 in??() >#70xf78ef508 in??() >#80x00b59fc0 in??() >#90xf78efa6c in??() >#10 0xf78ec248 in??() >#11 0xf78ec27c in??() >#12 0x00b489bd in??() >#13 0x0011e6e8 in??() >#14 0xf7a3f840 in??() >#15 0x00000000 in??() Because itdoesn't have, just asyou wrote yourself, any debugging symbols. Toget shown function names the binary must contain debug- ging informations. Ifyou run gdb onacore file you don't debug the binary onyour machine (which may have debugging information) but the binary that crashed onthe customers machine. Regards, Jens --\Jens Thoms Toerring ___ ******@ \__________________________ > Because it doesn't have, just as you wrote yourself, any debugging > symbols. To get shown function names the binary must contain debug- > ging informations. If you run gdb ona core file you don't debug > the binary on your machine (which may have debugging informati
