From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Bernhard Schmidt <berni@birkenwald.de>
Cc: Jan Engelhardt <jengelh@medozas.de>,
Krzysztof Oledzki <ole@ans.pl>,
netfilter-devel@vger.kernel.org
Subject: Re: conntrack segfault
Date: Thu, 02 Jul 2009 18:30:38 +0200 [thread overview]
Message-ID: <4A4CE0AE.9030901@netfilter.org> (raw)
In-Reply-To: <20090624221845.GA16585@pest>
Sorry for the late reply.
Bernhard Schmidt wrote:
> vex amd64->IR: unhandled instruction bytes: 0x6 0xDF 0xA1 0xBF 0x8 0x0
> ==24699== Invalid read of size 1
> ==24699== at 0x7FEFFD3E4: ???
> ==24699== by 0x7FEFFD3EB: ???
> ==24699== by 0x7FEFFD3F3: ???
> ==24699== Address 0x0 is not stack'd, malloc'd or (recently) free'd
> ==24699==
> ==24699== Process terminating with default action of signal 11 (SIGSEGV)
> ==24699== Access not within mapped region at address 0x0
> ==24699== at 0x7FEFFD3E4: ???
> ==24699== by 0x7FEFFD3EB: ???
> ==24699== by 0x7FEFFD3F3: ???
> ==24699==
> ==24699== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 2 from 1)
> Segmentation fault
>
> Does this help any more?
I still don't have a clear clue on what's wrong with this.
next prev parent reply other threads:[~2009-07-02 16:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-23 7:27 null-pointer deref in ulogd2 Bernhard Schmidt
2009-06-23 8:31 ` Bernhard Schmidt
2009-06-23 15:40 ` Pablo Neira Ayuso
2009-06-23 16:54 ` Bernhard Schmidt
2009-06-23 22:39 ` Bernhard Schmidt
2009-06-24 10:59 ` conntrack segfault (was: Re: null-pointer deref in ulogd2) Bernhard Schmidt
2009-06-24 11:17 ` Krzysztof Oledzki
2009-06-24 11:57 ` Jan Engelhardt
2009-06-24 12:56 ` conntrack segfault Bernhard Schmidt
2009-06-24 17:58 ` Pablo Neira Ayuso
2009-06-24 20:05 ` Bernhard Schmidt
2009-06-24 22:18 ` Bernhard Schmidt
2009-07-02 16:30 ` Pablo Neira Ayuso [this message]
2009-07-06 10:29 ` Krzysztof Oledzki
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=4A4CE0AE.9030901@netfilter.org \
--to=pablo@netfilter.org \
--cc=berni@birkenwald.de \
--cc=jengelh@medozas.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=ole@ans.pl \
/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).