Re: [Valgrind-users] Need support in debugging Valgrind 3.18 glibc segv error

[Paul F. <pj...@wa...>]

On 3/21/25 09:06, kiran hardas wrote:
> Hi Paul/Team,
>
> Thank you for your suggestion. I added the entry for shmget function 
> in coregrind/m_syswrap/syswrap-x86-linux.c
> and the error got resolved for shmget function. Yes it is x86 linux 
> that is getting used. Similar errors came for shmat, shmdt, shmctl 
> functions.
> I added similar entries of those functions too in the table and 
> resolved the errors.
>
> Currently i am getting error from shmat function as "Invalid argument" 
> from my application code.
> The data pointer returned by shmat function is coming as 0xffffffff 
> which is -1 (error). I am calling the shmat as below
>  in my application code
>
> data = shmat(shmid, NULL, 0);            /* where data is a struct 
> pointer and shmid is 1 obtained by a successful shmget call */
>
> I verified the arguments for this shmat function and they seem to be 
> fine. Also checked for permission issues.
> I am suspecting memory issue which could be resulting in shmat attach 
> failure after running valgrind (have glibc 2.40).
>
> Would appreciate any advice/suggestion you can provide for this issue.
>
Hi

I'll have a look this weekend.

A+

Paul