From: Josh Triplett <josht@linux.vnet.ibm.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: linux-sparse@vger.kernel.org
Subject: Re: random line shuffling test
Date: Wed, 01 Aug 2007 10:09:08 -0700 [thread overview]
Message-ID: <1185988148.3123.36.camel@josh-work.beaverton.ibm.com> (raw)
In-Reply-To: <20070730204200.GG5776@martell.zuzino.mipt.ru>
On Tue, 2007-07-31 at 00:42 +0400, Alexey Dobriyan wrote:
> On Sun, Jul 29, 2007 at 03:33:20PM +0400, Alexey Dobriyan wrote:
> > I'm currently running random line shuffling test taking, ha-ha, advansys.i
> > as input.
> >
> > Here is first trimmed testcase on which valgrind says stack overflow and
> > sparse segfaults.
> >
> >
> > int a, struct b c);
> > typedef void (elevator_activate_req_fn)(foo *);
> > typedef void (elevator_activate_req_fn)(struct foo *);
> > struct sigaction {
> > static struct lock_class_key __key;
> >
> >
> >
> > So far the joy is spoiled by many infinite loops sparse gets into and
> > automatic testing is still semi-automatic, but stay tuned.
>
> Here is another:
>
> __asm__("l" : "i" (1)
>
> #0 0x080543e4 in mark_assigned (expr=0x1) at evaluate.c:1388
> #1 0x080544ba in evaluate_assign_to (left=0xb749c2cc, type=0x80da040) at evaluate.c:1421
> #2 0x08058556 in evaluate_asm_statement (stmt=0xb7582888) at evaluate.c:3160
> #3 0x08058c63 in evaluate_statement (stmt=0xb7582888) at evaluate.c:3342
> #4 0x08058093 in evaluate_symbol (sym=0xb747d20c) at evaluate.c:3041
> #5 0x080580e9 in evaluate_symbol_list (list=0xb7dac30c) at evaluate.c:3054
> #6 0x080510cf in sparse (filename=0xbf9ff164 "a.c") at lib.c:786
> #7 0x0804bdac in main
Fuzz testing on Sparse seems like an *excellent* idea; thank you for
doing this. Nice finds.
- Josh Triplett
prev parent reply other threads:[~2007-08-01 17:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-29 11:33 random line shuffling test Alexey Dobriyan
2007-07-30 20:42 ` Alexey Dobriyan
2007-08-01 17:09 ` Josh Triplett [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1185988148.3123.36.camel@josh-work.beaverton.ibm.com \
--to=josht@linux.vnet.ibm.com \
--cc=adobriyan@gmail.com \
--cc=linux-sparse@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).