From: md@Linux.IT (Marco d'Itri)
To: linux-hotplug@vger.kernel.org
Subject: Bug#285281: core dump on amd64 (gcc-3.4)
Date: Wed, 15 Dec 2004 08:50:46 +0000 [thread overview]
Message-ID: <20041215085045.GA4444@wonderland.linux.it> (raw)
clsdev->directory is NULL, is this a bug in libsysfs or udev?
Apparently this only happens on amd64.
----- Forwarded message from martin-deb@zero-based.org -----
Subject: Bug#285281: core dump on amd64 (gcc-3.4)
Reply-To: martin-deb@zero-based.org, 285281@bugs.debian.org
From: martin-deb@zero-based.org
To: 285281@bugs.debian.org
Cc: Harald Dunkel <harald.dunkel@t-online.de>
On Sun, Dec 12, 2004 at 11:27:48AM +0100, Marco d'Itri wrote:
> On Dec 12, Harald Dunkel <harald.dunkel@t-online.de> wrote:
>
> > There seems to be something wrong with udev at least on
> > amd64 (gcc-3.4).
>
> Please do your best to get a stack trace, possibly from the unstripped
> binary.
I see the same behavior on amd64 with gcc-3.3. Here is a stacktrace:
GNU gdb 6.3-debian
[...]
Core was generated by `udev vc'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /lib/libc.so.6...done.
Loaded symbols for /lib/libc.so.6
Reading symbols from /lib/ld-linux-x86-64.so.2...done.
Loaded symbols for /lib64/ld-linux-x86-64.so.2
#0 0x0000000000403024 in sysfs_get_classdev_attr (clsdev=0x518260, name=0x40dcac "dev") at libsysfs/sysfs_class.c:643
643 if (clsdev->directory->subdirs = NULL)
(gdb) backtrace
#0 0x0000000000403024 in sysfs_get_classdev_attr (clsdev=0x518260, name=0x40dcac "dev") at libsysfs/sysfs_class.c:643
#1 0x000000000040904e in get_major_minor (class_dev=0x0, udev=0x7fbffff330) at udev_add.c:57
#2 0x0000000000409874 in udev_add_device (udev=0x7fbffff330, class_dev=0x518260) at udev_add.c:287
#3 0x0000000000402009 in main (argc=2, argv=0x7fbffffdb8, envp=0x0) at udev.c:197
(gdb) print *clsdev
$1 = {name = "vcs1", '\0' <repeats 45 times>, classname = "vc", '\0' <repeats 47 times>,
path = "/sys/class/vc/vcs1", '\0' <repeats 236 times>, parent = 0x0, sysdevice = 0x0, driver = 0x0, directory = 0x0}
Martin
----- End forwarded message -----
--
ciao, |
Marco | [9803 vebcDBN29Lxms]
-------------------------------------------------------
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://productguide.itmanagersjournal.com/
_______________________________________________
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
next reply other threads:[~2004-12-15 8:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-15 8:50 Marco d'Itri [this message]
2004-12-15 12:25 ` Bug#285281: core dump on amd64 (gcc-3.4) Marco d'Itri
2004-12-15 13:27 ` Kay Sievers
2004-12-15 16:40 ` Daniel Stekloff
2004-12-16 4:55 ` Ananth N Mavinakayanahalli
2004-12-16 7:20 ` Kay Sievers
2004-12-17 19:07 ` 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=20041215085045.GA4444@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).