Bug 249794 - Clicking on one Device after the other causes a crash in hardinfo
Summary: Clicking on one Device after the other causes a crash in hardinfo
Alias: None
Product: Fedora
Classification: Fedora
Component: hardinfo   
(Show other bugs)
Version: rawhide
Hardware: x86_64 Linux
Target Milestone: ---
Assignee: Adel Gadllah
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2007-07-27 02:21 UTC by Deji Akingunola
Modified: 2007-11-30 22:12 UTC (History)
0 users

Fixed In Version: hardinfo-
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-08-15 12:39:49 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
hardinfo backtrace (12.40 KB, application/octet-stream)
2007-07-27 12:19 UTC, Deji Akingunola
no flags Details
hardinfo full backtrace (31.18 KB, text/plain)
2007-07-28 03:35 UTC, Deji Akingunola
no flags Details
stderr output (1.11 KB, text/plain)
2007-07-31 12:21 UTC, Deji Akingunola
no flags Details
hardinfo crash backtrace (32.56 KB, text/plain)
2007-07-31 14:03 UTC, Deji Akingunola
no flags Details
hardinfo crash backtrace (36.83 KB, text/plain)
2007-08-02 14:55 UTC, Deji Akingunola
no flags Details

Description Deji Akingunola 2007-07-27 02:21:54 UTC
Description of problem: Successive click on any two Device on the left pane of
hardinfo causes it to crash. I started it on the terminal and was the trace
below after it crashed.
[deji@agape ~]$ hardinfo
*** glibc detected *** hardinfo: double free or corruption (out):
0x000000000087ca60 ***
======= Backtrace: =========
======= Memory map: ========
00400000-00420000 r-xp 00000000 fd:00 2084310                           
00620000-00622000 rw-p 00020000 fd:00 2084310                           
00622000-008e9000 rw-p 00622000 00:00 0                                  [heap]
3115c00000-3115c1a000 r-xp 00000000 fd:00 9339177                       
3115e1a000-3115e1b000 r--p 0001a000 fd:00 9339177                       
3115e1b000-3115e1c000 rw-p 0001b000 fd:00 9339177                       
3116000000-3116051000 r-xp 00000000 fd:00 2069981                       
3116051000-3116250000 ---p 00051000 fd:00 2069981                       
3116250000-3116261000 rw-p 00050000 fd:00 2069981                       
3116400000-3116479000 r-xp 00000000 fd:00 2078450                       
3116479000-3116678000 ---p 00079000 fd:00 2078450                       
3116678000-3116682000 rw-p 00078000 fd:00 2078450                       
3116c00000-3116d47000 r-xp 00000000 fd:00 9339178                       
3116d47000-3116f47000 ---p 00147000 fd:00 9339178                       
3116f47000-3116f4b000 r--p 00147000 fd:00 9339178                       
3116f4b000-3116f4c000 rw-p 0014b000 fd:00 9339178                       
3116f4c000-3116f51000 rw-p 3116f4c000 00:00 0 
3117000000-3117082000 r-xp 00000000 fd:00 9339179                       
3117082000-3117281000 ---p 00082000 fd:00 9339179                       
3117281000-3117282000 r--p 00081000 fd:00 9339179                       
3117282000-3117283000 rw-p 00082000 fd:00 9339179                       
3117400000-3117402000 r-xp 00000000 fd:00 9339180                       
3117402000-3117602000 ---p 00002000 fd:00 9339180                       
3117602000-3117603000 r--p 00002000 fd:00 9339180                       
3117603000-3117604000 rw-p 00003000 fd:00 9339180                       
3117800000-3117814000 r-xp 00000000 fd:00 9339184                       
3117814000-3117a13000 ---p 00014000 fd:00 9339184                       
3117a13000-3117a14000 rw-p 00013000 fd:00 9339184                       
3117c00000-3117c05000 r-xp 00000000 fd:00 12126Aborted
[deji@agape ~]$ 

Version-Release number of selected component (if applicable):

How reproducible: Always

Steps to Reproduce:
Actual results:

Expected results:

Additional info:

Comment 1 Adel Gadllah 2007-07-27 08:00:28 UTC
I can't reproduce this here. Can you generate a proper backtrace?
1) Install hardinfo-debuginfo
2) Open a Terminal and type gdb
3) type file /usr/bin/hardinfo
4) type r
5) reproduce the crash
6) type bt full
7) copy and attach the output.

Comment 2 Adel Gadllah 2007-07-27 08:47:33 UTC
Can you reproduce it with this version?

Comment 3 Deji Akingunola 2007-07-27 12:19:00 UTC
Created attachment 160112 [details]
hardinfo backtrace

Comment 4 Deji Akingunola 2007-07-27 12:19:57 UTC
I got the latest version for rawhide (hardinfo- from koji. It
seems I'll need to install other debuginfo rpms to really get a full backtrace.
However following the steps you outline above, i got the attached backtrace.

Comment 5 Adel Gadllah 2007-07-27 17:47:01 UTC
thx for the backtrace but its useless without the other debuginfo packages...
can you install them and recreate it?
also does this happen for all devices?

Comment 6 Deji Akingunola 2007-07-28 03:35:13 UTC
Created attachment 160154 [details]
hardinfo full backtrace

Here is the full backtrace. It happens for any 2 devices, selecting one after
the other.

Comment 7 Adel Gadllah 2007-07-30 07:54:23 UTC
does this build fix it for you?

Comment 8 Deji Akingunola 2007-07-30 12:39:57 UTC
It crashed similarly.

Comment 9 Adel Gadllah 2007-07-31 07:34:34 UTC
Ok, please run this and redirect stderr output to a file and attach it here.
1) Open a terminal
2) type
hardinfo 2>debug.log
3) attach this file here

Comment 10 Deji Akingunola 2007-07-31 12:21:52 UTC
Created attachment 160308 [details]
stderr output

Comment 11 Deji Akingunola 2007-07-31 12:23:35 UTC
Requested info attached.

Comment 12 Adel Gadllah 2007-07-31 12:26:52 UTC
has this info been created while reproducing the crash?

Comment 13 Deji Akingunola 2007-07-31 12:32:13 UTC
Yes, but oddly enough it doesn't seem to contain any information about the crash
itself. I can provide you the full baktrace too if you want, it's no much
different from the earlier one.

Comment 14 Adel Gadllah 2007-07-31 13:48:56 UTC
ok, please attach it too ... it wont hurt

Comment 15 Deji Akingunola 2007-07-31 14:03:19 UTC
Created attachment 160320 [details]
hardinfo crash backtrace

Produced with hardinfo-

Comment 16 Adel Gadllah 2007-08-02 08:04:12 UTC
Please try this build (it should fix it):

Comment 17 Deji Akingunola 2007-08-02 14:55:33 UTC
Created attachment 160527 [details]
hardinfo crash backtrace

Unfortunately, it still crashes as before. I've attached the backtrace gotten
with hardinfo-; this time I selected 'Memory' first
and then 'PCI Devices' next (the same crash always occur with any selecting any
device first, followed by another).

Comment 18 Adel Gadllah 2007-08-15 07:52:12 UTC
Sorry for the delay.
Can you try this build:
I was able to reproduce this on F8-Test1 and created this patch (was working for
me). Please confirm if it works for you too or not.

Comment 19 Deji Akingunola 2007-08-15 09:35:31 UTC
Unfortunately no, hardinfo- still doesn't work for me,
similar crash.

Comment 20 Adel Gadllah 2007-08-15 11:03:13 UTC
ok thx for testing.
can you try this build after finished building:

Comment 21 Deji Akingunola 2007-08-15 12:39:49 UTC
Phew, at last hardinfo- DOES WORK :). Thanks for your
efforts at resolving this.

Note You need to log in before you can comment on or make changes to this bug.