From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: new auparse question
Date: Wed, 31 Aug 2011 16:49:46 -0400 [thread overview]
Message-ID: <201108311649.46375.sgrubb@redhat.com> (raw)
In-Reply-To: <1314822708.2094.127.camel@lcb>
On Wednesday, August 31, 2011 04:31:48 PM LC Bruzenak wrote:
> So my question is - is this a bug (I would think so) or should I always
> precede any auparse call sequence with at least one fresh
> auparse_first_field call?
A segfault is a bug as far as this library is concerned. I know other libraries let
you segfault if you do something wrong. I'll try to make a reproducer and see what's
going on.
-Steve
next prev parent reply other threads:[~2011-08-31 20:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-31 20:31 new auparse question LC Bruzenak
2011-08-31 20:49 ` Steve Grubb [this message]
2011-09-01 0:55 ` Steve Grubb
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=201108311649.46375.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.com \
/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.