linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: md@Linux.IT (Marco d'Itri)
To: linux-hotplug@vger.kernel.org
Subject: Bug#298192: udev: segfault with new rule on startup
Date: Mon, 07 Mar 2005 23:03:05 +0000	[thread overview]
Message-ID: <20050307230305.GA16754@wonderland.linux.it> (raw)

This rule causes udevstart 054 to segfault:

BUS="pci", SUBSYSTEM="net", DRIVER="ipw2100", NAME="wlan"

----- Forwarded message from Thomas Breitner <debian@tombreit.de> -----

Subject: Bug#298192: udev: segfault with new rule on startup
Reply-To: debian@tombreit.de, 298192@bugs.debian.org
From: Thomas Breitner <debian@tombreit.de>
To: 298192@bugs.debian.org

Thanks, here it is:

mala:~/sourcen/udev-0.054# /etc/init.d/udev restart
Recreating device nodes.../etc/init.d/udev: line 216: 10361 Segmentation fault      udevstart
mala:~/sourcen/udev-0.054# gdb /sbin/udevstart
GNU gdb 6.3-debian
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-linux"...Using host libthread_db library "/lib/tls/libthread_db.so.1".

(gdb) run
Starting program: /sbin/udevstart

Program received signal SIGSEGV, Segmentation fault.
strcmp_pattern (p=0x805cc60 "ipw2100", s=0x1c4 <Address 0x1c4 out of bounds>) at namedev.c:50
50              if (s[0] = '\0') {
(gdb) where
#0  strcmp_pattern (p=0x805cc60 "ipw2100", s=0x1c4 <Address 0x1c4 out of bounds>) at namedev.c:50
#1  0x0804e448 in match_rule (udev=0xbfffdd30, dev=0x805c5d8, class_dev=0x8059168, sysfs_device=0x0) at namedev.c:597
#2  0x0804e52b in namedev_name_device (udev=0xbfffdd30, class_dev=0x8059168) at namedev.c:724
#3  0x0804b262 in udev_add_device (udev=0xbfffdd30, class_dev=0x8059168) at udev_add.c:284
#4  0x0804b97b in add_device (path=0x8059168 "event0", subsystem=0x809eb60 "input") at udev_start.c:112
#5  0x0804bb35 in exec_list (device_list=0xbfffe758) at udev_start.c:155
#6  0x0804be70 in udev_scan_class () at udev_start.c:278
#7  0x0804c034 in udev_start () at udev_start.c:287
#8  0x080499e4 in main (argc=1, argv=0xbffff9b4, envp=0xbffff9bc) at udev.c:149
(gdb)

tschuess,
thomas



Am Montag, den 07.03.2005, 20:18 +0100 schrieb Marco d'Itri:
> On Mar 06, Thomas Breitner <debian@tombreit.de> wrote:
> 
> > Don't know how to enable debugging symbols, can't find it in rules.
> > Please let me know how to enable them...
> Just build the package with "./debian/rules build" and copy
> build-tree/udev-054/udev to /sbin/udev .
> 
> Then run "gdb /sbin/udevstart" and use the commands "run" and "where".
> 
-- 
_____________________________________________
Thomas Breitner

mail@tombreit.de   |   http://www.tombreit.de


----- End forwarded message -----

-- 
ciao,
Marco


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

             reply	other threads:[~2005-03-07 23:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-07 23:03 Marco d'Itri [this message]
2005-03-08  0:43 ` Bug#298192: udev: segfault with new rule on startup Kay Sievers
2005-03-08  6:53 ` Greg KH

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=20050307230305.GA16754@wonderland.linux.it \
    --to=md@linux.it \
    --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).