Re: [bug, bisected, -chrisl] Segfault at evaluate.c:341

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Mar 19, 2009 at 12:14 PM, Al Viro <viro@xxxxxxxxxxxxxxxxxx> wrote:
> a) some <expletives> has #define if(x) ....... (check it out, I'm not kidding)
> b) ifdef that turd's conditional upon is present in your .config
> c) ... and now,
>        if (
> #ifdef .....
>                barf &&
> #endif
>                vomit)
>
> steps into undefined behaviour.

We can complain about the bad C code.

We should stop the segfault though. I take a look at it. It seems that
there is a SYM_NODE with base_type is NULL. I guess in some of
the error path we result in an invalid AST three.

Maybe we should abort sparse after "too many error" ?

Chris
--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Newbies FAQ]     [LKML]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Trinity Fuzzer Tool]

  Powered by Linux