From: Matthias Schwarzott <zzam@gentoo.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev-131 strange segfault
Date: Fri, 07 Nov 2008 18:54:14 +0000 [thread overview]
Message-ID: <200811071954.14631.zzam@gentoo.org> (raw)
In-Reply-To: <200811071307.11884.zzam@gentoo.org>
On Freitag, 7. November 2008, Kay Sievers wrote:
> On Fri, Nov 7, 2008 at 13:07, Matthias Schwarzott <zzam@gentoo.org> wrote:
> > I managed to let udev-131 segfault at startup.
> >
> > I configured it like this:
> > CFLAGS="-Wall -ggdb" ./configure --prefix=/usr --sysconfdir=/etc
> > --exec-prefix> >
> > Running it in gdb shows it segfaults at udev-rules.c:831
> >
> > (gdb) run
> > Starting program: /tmp/udev-131/udev/udevd
> >
> > Program received signal SIGSEGV, Segmentation fault.
> > 0x0804ea06 in get_key (udev=0x9175008, line=0xafcdc8f0, key=0xafcdc5d8,
> > op=0xafcdc5d0, value=0xafcdc5d4)
> > at udev-rules.c:831
> > 831 dbg(udev, "%s '%s'-'%s'\n", operation_str[*op], *key,
> > *value);
>
> Adding "-O2" to the CFLAGS makes it work, right?
>
Yes, this works.
Regards
Matthias
prev parent reply other threads:[~2008-11-07 18:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-07 12:07 udev-131 strange segfault Matthias Schwarzott
2008-11-07 13:42 ` Kay Sievers
2008-11-07 18:54 ` Matthias Schwarzott [this message]
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=200811071954.14631.zzam@gentoo.org \
--to=zzam@gentoo.org \
--cc=linux-hotplug@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 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).