From: Edward Shishkin <edward.shishkin@gmail.com>
To: Vidra.Jonas@seznam.cz
Cc: reiserfs-devel@vger.kernel.org
Subject: Re: Segfault in fsck.reiser4
Date: Wed, 24 Mar 2010 14:10:26 +0100 [thread overview]
Message-ID: <4BAA0F42.90308@gmail.com> (raw)
In-Reply-To: <7880.2170.3389-28898-1298266740-1269420891@seznam.cz>
Vidra.Jonas@seznam.cz wrote:
> Dne Tue, 23 Mar 2010 23:31:48 +0100 Edward Shishkin
> <edward.shishkin@gmail.com> napsal(a):
>
>> Segfault is caused by aux_adler32: offset (4294839597) is out of
>> bounds..
>> Could you print and show us the structure "hint"?
>
> (gdb) print hint
> No symbol "hint" in current context.
try to jump several levels up: the function ccreg40_check_cluster
has an argument ccreg40_hint_t *hint, it shouldn't be optimized.
>
> Am I doing it right or should I set a breakpoint somewhere before the
> crash?
next prev parent reply other threads:[~2010-03-24 13:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-23 17:30 Segfault in fsck.reiser4 Jonáš Vidra
2010-03-23 20:26 ` Edward Shishkin
2010-03-23 20:31 ` Edward Shishkin
2010-03-23 21:43 ` Jonáš Vidra
2010-03-23 22:31 ` Edward Shishkin
2010-03-24 8:54 ` Vidra.Jonas
2010-03-24 13:10 ` Edward Shishkin [this message]
2010-03-27 8:38 ` Jonáš Vidra
2010-03-30 0:59 ` Edward Shishkin
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=4BAA0F42.90308@gmail.com \
--to=edward.shishkin@gmail.com \
--cc=Vidra.Jonas@seznam.cz \
--cc=reiserfs-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.