Re: [Valgrind-users] Syscall param unlink(pathname) points to unaddressable byte(s)

[poornima b. <poo...@gm...>]

Thank you Paul, you are right there was null parameter being passed to
unlink in my code.
I fixed the issue in my code.
Thanks alot for your time :)

On Wed, Dec 14, 2011 at 5:09 PM,  <pa...@fr...> wrote:
> ----- Original Message -----
>> Dear Valgrind-team,
>>
>> I am getting following error when i run valgrind on my code.
>> I want to understand what this error means and how to fix it.
>> In the below code we pass valid file name to SetOutputMetaFile
>> function. The code looks fine to me
>> but no idea why this error is reported by valgrind. Please help me to
>> understand this error.
>
>> ==16368== Syscall param unlink(pathname) points to unaddressable
>> byte(s)
>> ==16368==    at 0x8C6DB2: unlink (in /lib/libc-2.7.so)
>> ==16368==    by 0x4171EA0: vml::CVMLib::SetOutputMetaFile(char
> ...
>> ==16368==    by 0x8049A22: main (in
>> /home/sface/SFacePlusRegularTest/VMLibraryTesting/111207_suraj/VMAPIUnitTest/VMAPIUnitTest/VMAPIUnitTest)
>> ==16368==  Address 0x0 is not stack'd, malloc'd or (recently) free'd
>>
>> I am using valgrind3.4.1 version on GNU/Linux system.
>
> Valgrind is saying that the path argument of unlink is null. Are you sure that the version you are testing with Valgrind has a non-null path?
>
> Have you tried attaching a debugger to display path?
>
> Paul