From: Pavel Roskin <proski@gnu.org>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Christopher Li <sparse@chrisli.org>,
linux-sparse@vger.kernel.org,
Morten Welinder <mwelinder@gmail.com>
Subject: Re: sparse segfault in kernel -mm tree
Date: Tue, 06 Mar 2007 22:02:04 -0500 [thread overview]
Message-ID: <1173236524.5140.31.camel@dv> (raw)
In-Reply-To: <118833cc0703061843s22d35a9ei17fd48f97fc7626a@mail.gmail.com>
On Tue, 2007-03-06 at 21:43 -0500, Morten Welinder wrote:
> Try running sparse under valgrind to see if there is some memory
> corruption at an
> earlier stage.
Randy,
maybe you'll just post the .i file as is (perhaps compressed with
bzip2)? It looks like your post has generated lots of interest, but
nobody can reproduce the problem. It's a much bigger waste of bandwidth
to have others download the -mm kernel.
If the file is too large for the list, please send it to me, and I'll
put it online. Or put that file on pastebin.com or turboupload.com.
If I can reproduce the bug, with or without valgrind, I'll reduce the
file to the minimal required for the bug to be see. I did it before.
If sparse crashes for you only, then you'll need to debug it on your
system, and it doesn't matter how big the file is. What matters is the
backtrace and other info from gdb.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2007-03-07 3:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 1:53 sparse segfault in kernel -mm tree Randy Dunlap
2007-03-06 2:33 ` Christopher Li
2007-03-06 5:04 ` Randy Dunlap
2007-03-06 5:42 ` Pavel Roskin
2007-03-06 6:40 ` Randy Dunlap
2007-03-06 18:19 ` Pavel Roskin
2007-03-06 20:58 ` Randy Dunlap
2007-03-06 22:28 ` Christopher Li
2007-03-06 23:12 ` Randy Dunlap
2007-03-07 2:43 ` Morten Welinder
2007-03-07 3:02 ` Pavel Roskin [this message]
2007-03-07 3:04 ` Randy Dunlap
2007-03-07 3:12 ` Christopher Li
2007-03-07 3:51 ` Dave Jones
2007-03-07 4:13 ` Randy Dunlap
2007-03-07 4:27 ` Randy Dunlap
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=1173236524.5140.31.camel@dv \
--to=proski@gnu.org \
--cc=linux-sparse@vger.kernel.org \
--cc=mwelinder@gmail.com \
--cc=rdunlap@xenotime.net \
--cc=sparse@chrisli.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).