|
From: Andy G. <and...@co...> - 2009-07-14 22:11:58
|
I saw earlier posts today where a user is not seeing source information in the valgrind output. I'm experiencing the same problem on one machine but not on another (with the same binary version of my library that I am testing). Here is the output on the server that does not show the source information: ==3821== 195,899 bytes in 13,600 blocks are definitely lost in loss record 77 of 78 ==3821== at 0x4A06497: operator new[](unsigned long) (vg_replace_malloc.c:274) ==3821== by 0x9DFCB9D: ??? ==3821== by 0x9DFED2B: ??? ==3821== by 0x9E0EE41: ??? ==3821== by 0x9DFB9BD: ??? ==3821== by 0x9E10EB5: ??? ==3821== by 0x9E6FE46: ??? ==3821== by 0x9E673B6: ??? ==3821== by 0x9E4ECFA: ??? ==3821== by 0xAD2D3CC: ??? ==3821== by 0x5CEA11: zend_do_fcall_common_helper_SPEC (in /usr/bin/ php) ==3821== by 0x5BE80B: execute (in /usr/bin/php) My C library is called from PHP on both servers. Both servers are CentOS 5.2 but slightly different revisions. I'd like to know what I need to do to get the source/line number information to display on the server that is not currently displaying that information. I saw a suggestion about install debug versions if libstdc++ but I don't seem to have those installed on the server where this is working correctly. I'd appreciate any pointers on how to resolve this. Thanks, Andy. |