On 23/04/14 17:02, Michael O'Donnell wrote:
>
>
> > Hi Michael, thanks for the info. We are at the moment struggling
> > to bring this package to some releasable state and having a
> > bug that is not FTBFS, is actually a good thing!
> >
> > Can you confirm your bug with the version 21.3-1 that is now
> > in unstable?
>
>
> [ Sorry for the delayed response... ]
>
> Yes, I upgraded hwinfo to 21.3-1 and the fault still occurs:
>
> # hwinfo
> > floppy.1: get nvram*** stack smashing detected ***: hwinfo terminated
> Segmentation fault
>
>
>
> --Michael O'Donnell mod.report...@b0rken.com
>
Aha, ok. We'll need more info to trace it. My questions are:
1) do you have a custom kernel (especially in respect to nvram modules)?
2) do you have a floppy?
3) does hwinfo --floppy work for you ? what about hwinfo --cpu?
4) does it happen with "sudo hwinfo" (if you dare to run it)?
5) some more debug would be appreciated; can you provide a stacktrace
for the segfault (by compiling with debugging symbols or something
similar); also, it makes me wonder whether we should provide hwinfo-dbg...
Well, it seems to be related to:
http://lists.opensuse.org/opensuse-factory/2012-08/msg00099.html
The problem seems to be in the function read_klog@klog.c. Looking at the code,
a bug is highly possible.
Funny thing is that if I run "hwinfo --floppy" I get no output, but when I
"modprobe nvram" then
I get this:
[ /dev ] $ hwinfo --floppy
02: Floppy 00.0: 10603 Floppy Disk
[Created at floppy.120]
Unique ID: sPPV.oZ89vuho4Y3
Parent ID: rdCR.3wRL2_g4d2B
Hardware Class: floppy
Model: "Floppy Disk"
Device File: /dev/fd0
Size: 3.5 ''
Size: 2880 sectors a 512 bytes
Capacity: 0 GB (1474560 bytes)
Drive status: no medium
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #1 (Floppy disk controller)
But it does not crash in both cases.
Cheers,
Tomasz
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
