linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christopher Li <sparse@chrisli.org>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Josh Triplett <josh@joshtriplett.org>,
	Dan Carpenter <error27@gmail.com>,
	linux-sparse@vger.kernel.org
Subject: Re: segfault in sparse snapshot 2010-02-13
Date: Thu, 25 Mar 2010 10:20:30 -0700	[thread overview]
Message-ID: <70318cbf1003251020j11ad7dd9m5e22b52699265526@mail.gmail.com> (raw)
In-Reply-To: <4BAB8F36.2090600@xenotime.net>

On Thu, Mar 25, 2010 at 9:28 AM, Randy Dunlap <rdunlap@xenotime.net> wrote:
>
> OK, I emailed that file, but it's huge -- it probably won't be on the
> mailing list, so I also uploaded it to here:
>  http://www.xenotime.net/linux/doc/br_fdb.i

Thanks, I can duplicate the segfault now.

Looking at it.

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

  reply	other threads:[~2010-03-25 17:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-24 17:41 segfault in sparse snapshot 2010-02-13 Randy Dunlap
2010-03-24 19:36 ` Josh Triplett
     [not found]   ` <4BAA6C4C.8010103@xenotime.net>
2010-03-24 20:34     ` Josh Triplett
2010-03-24 21:01       ` Randy Dunlap
2010-03-24 22:00         ` Josh Triplett
2010-03-24 22:02           ` Randy Dunlap
2010-03-25 10:49       ` Dan Carpenter
2010-03-25 15:46         ` Josh Triplett
2010-03-25 16:28           ` Randy Dunlap
2010-03-25 17:20             ` Christopher Li [this message]
2010-03-29  7:50               ` Christopher Li
2010-03-29 16:46                 ` Randy Dunlap
2010-03-29 17:29                   ` Christopher Li

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=70318cbf1003251020j11ad7dd9m5e22b52699265526@mail.gmail.com \
    --to=sparse@chrisli.org \
    --cc=error27@gmail.com \
    --cc=josh@joshtriplett.org \
    --cc=linux-sparse@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    /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).