Re: the sigsegv issue with recent smatch

> On 26. Nov 2025, at 14:55, Dan Carpenter <[email protected]> =
wrote:
>=20
> On Tue, Nov 25, 2025 at 06:27:06PM +0200, Toomas Soome wrote:
>> I got a bit background for sigsegv case.
>>=20
>=20
> Do you have a reproducer script I could try?  I think your
> reading of the code is correct.  It's trying to take the
> something like:
>=20
> 	x =3D frob(a, b, c, d);
>=20
> and create a fake assignment:
>=20
> 	x =3D d;
>=20
> And, I guess, it can't find 'd'.  But my line numbers in mdb_nv.c are
> different from yours.
>=20
> There seems to be an obvious fix which I have done and pushed
> but I can't test it.  Could you give it a shot?
> =
https://github.com/error27/smatch/commit/4dca0c1677879bf9a86b2311bf1ba75ac=
fdf82ba
>=20
> regards,
> dan carpenter
>=20

I just did pull latest head and yes, it did fix all the SIGSEGV cases. I =
will try to see if I can create some usable sample=E2=80=A6 on whole =
code tree there was just about 5 cases of SIGSEGV, so it may need some =
effort;)

thanks,
toomas=