| commit | f7e7d7cbad5b04136abbfed66726d99dd84af526 | |
| author | Al Viro <viro@ZenIV.linux.org.uk> | |
| Thu, 19 Mar 2009 22:09:06 +0000 (19 22:09 +0000) | ||
| committer | Christopher Li <sparse@chrisli.org> | |
| Sat, 18 Jul 2009 05:30:10 +0000 (18 05:30 +0000) | ||
| tree | dac371d4168be65eccd230f24e482f138876ae5e | treesnapshot (tar.gz zip) |
| parent | b608ddfe1816826b5061a5513c0df3c2de2db905 | commitdiff |
Segfault at evaluate.c:341
On Thu, Mar 19, 2009 at 09:52:50PM +0000, Al Viro wrote:
Yeah... It's an old b0rken handling of calls for K&R + changes that exposed
that even worse.
Status quo is restored by the patch below, but it's a stopgap - e.g.
void f();
void g(void)
{
f(0, 0);
}
will warn about extra arguments as if we had void f(void); as sparse had
been doing all along. B0rken.
Testcase for the segfault is
void f(x, y);
void g(void)
{
f(0, 0);
}
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Signed-off-by: Christopher Li <sparse@chrisli.org>
On Thu, Mar 19, 2009 at 09:52:50PM +0000, Al Viro wrote:
Yeah... It's an old b0rken handling of calls for K&R + changes that exposed
that even worse.
Status quo is restored by the patch below, but it's a stopgap - e.g.
void f();
void g(void)
{
f(0, 0);
}
will warn about extra arguments as if we had void f(void); as sparse had
been doing all along. B0rken.
Testcase for the segfault is
void f(x, y);
void g(void)
{
f(0, 0);
}
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Signed-off-by: Christopher Li <sparse@chrisli.org>
| parse.c | diffblobblamehistory |