Re: [Valgrind-users] full path to source

2011-03-21 Thread Osman, Ahmed
: [Valgrind-users] full path to source On Thu, Mar 17, 2011 at 11:59 PM, Osman, Ahmed ahmed_os...@mentor.com wrote: Is there a way  to make valgrind report the full path of the source code? See also the documentation of --fullpath-after= here: http://www.valgrind.org/docs/manual/manual-core.html#manual

Re: [Valgrind-users] full path to source

2011-03-21 Thread Bart Van Assche
and I don't see it -Original Message- From: bart.vanass...@gmail.com [mailto:bart.vanass...@gmail.com] On Behalf Of Bart Van Assche Sent: Friday, March 18, 2011 4:14 AM To: Osman, Ahmed Cc: valgrind-users@lists.sourceforge.net Subject: Re: [Valgrind-users] full path to source On Thu

Re: [Valgrind-users] full path to source

2011-03-18 Thread Bart Van Assche
On Thu, Mar 17, 2011 at 11:59 PM, Osman, Ahmed ahmed_os...@mentor.com wrote: Is there a way  to make valgrind report the full path of the source code? See also the documentation of --fullpath-after= here: http://www.valgrind.org/docs/manual/manual-core.html#manual-core.options. Bart.

[Valgrind-users] full path to source

2011-03-17 Thread Osman, Ahmed
Hi All, Usually Valgrind reports the source file with line number in its trace ==787== Invalid read of size 2 ==787== at 0x8AB4D25: nsaParseHierString (NamespaceAccess.c:974) ==787== by 0x8AB586D: nsaCreateSubelementIndexList (NamespaceAccess.c:1491) ==787== by 0x86F8A1E: isMemoryObject