dmidecode-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[dmidecode] Crash bug in dmidecde 2.5?


From: Petter Reinholdtsen
Subject: [dmidecode] Crash bug in dmidecde 2.5?
Date: Thu, 10 Feb 2005 08:41:43 +0100

On one of our machines, dmidecode crashes.  I found the problem
reported on
<URL:https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=112355>, and
added some information there.  I tested the CVS version, and got this
backtrace:

(gdb) run
Starting program: /usr/src/dmidecode/dmidecode/dmidecode
# dmidecode 2.5
SMBIOS 2.3 present.
96 structures occupying 5510 bytes.
Table at 0xDFF9C340.

Program received signal SIGSEGV, Segmentation fault.
0x001f017a in memcpy () from /lib/tls/libc.so.6
(gdb) bt
#0  0x001f017a in memcpy () from /lib/tls/libc.so.6
#1  0x0804f3ae in mem_chunk (base=-537279680, len=5510,
    devmem=0x8053b48 "/dev/mem") at util.c:136
#2  0x0804ed6f in dmi_table (base=3757687616, len=5510, num=96, 
ver=515,
    devmem=0x8053b48 "/dev/mem") at dmidecode.c:3746
#3  0x0804ef84 in smbios_decode (buf=0x9c37fe8 
"_SM_\f\037\002\003q\001",
    devmem=0x8053b48 "/dev/mem") at dmidecode.c:3796
#4  0x0804f1f0 in main (argc=1, argv=0xbfff9554) at dmidecode.c:3925
(gdb)

If the comment in RedHats bugzilla is correct, the problem is a
signed/unsigned issue.  Notice the negative base value sent to
mem_chunk().

What is the best fix for this?




reply via email to

[Prev in Thread] Current Thread [Next in Thread]