Bug 1409005

Summary: [abrt] lshw: snprintf(): lshw killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Thanh lam NGUYEN <ntl67br>
Component: lshwAssignee: Terje Røsten <terje.rosten>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: terje.rosten
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/8e4efbe0df2b0c7468001080a5e58961452df676
Whiteboard: abrt_hash:10f65eb370642df58717482ba2c85a87284cf5f5;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-08 19:30:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Thanh lam NGUYEN 2016-12-28 21:47:39 UTC
Description of problem:
en lancant la commande en tant que "root".

Version-Release number of selected component:
lshw-B.02.18-5.fc24

Additional info:
reporter:       libreport-2.7.2
backtrace_rating: 4
cmdline:        lshw
crash_function: snprintf
executable:     /usr/sbin/lshw
global_pid:     1485
kernel:         4.8.15-200.fc24.x86_64
pkg_fingerprint: 73BD E983 81B4 6521
pkg_vendor:     Fedora Project
runlevel:       N 5
type:           CCpp
uid:            500

Truncated backtrace:
Thread no. 1 (10 frames)
 #3 snprintf at /usr/include/bits/stdio2.h:65
 #4 hwNode::setPhysId at hw.cc:1110
 #5 analyse_dosextpart at partitions.cc:417
 #6 analyse_dospart at partitions.cc:452
 #7 analyse_dosextpart at partitions.cc:420
 #8 analyse_dospart at partitions.cc:452
 #9 analyse_dosextpart at partitions.cc:420
 #10 analyse_dospart at partitions.cc:452
 #11 analyse_dosextpart at partitions.cc:420
 #12 analyse_dospart at partitions.cc:452

Comment 1 Thanh lam NGUYEN 2016-12-28 21:47:47 UTC
Created attachment 1235732 [details]
File: backtrace

Comment 2 Thanh lam NGUYEN 2016-12-28 21:47:48 UTC
Created attachment 1235733 [details]
File: cgroup

Comment 3 Thanh lam NGUYEN 2016-12-28 21:47:50 UTC
Created attachment 1235734 [details]
File: core_backtrace

Comment 4 Thanh lam NGUYEN 2016-12-28 21:47:52 UTC
Created attachment 1235735 [details]
File: dso_list

Comment 5 Thanh lam NGUYEN 2016-12-28 21:47:53 UTC
Created attachment 1235736 [details]
File: environ

Comment 6 Thanh lam NGUYEN 2016-12-28 21:47:54 UTC
Created attachment 1235737 [details]
File: exploitable

Comment 7 Thanh lam NGUYEN 2016-12-28 21:47:55 UTC
Created attachment 1235738 [details]
File: limits

Comment 8 Thanh lam NGUYEN 2016-12-28 21:47:57 UTC
Created attachment 1235739 [details]
File: maps

Comment 9 Thanh lam NGUYEN 2016-12-28 21:47:58 UTC
Created attachment 1235740 [details]
File: mountinfo

Comment 10 Thanh lam NGUYEN 2016-12-28 21:47:59 UTC
Created attachment 1235741 [details]
File: namespaces

Comment 11 Thanh lam NGUYEN 2016-12-28 21:48:00 UTC
Created attachment 1235742 [details]
File: open_fds

Comment 12 Thanh lam NGUYEN 2016-12-28 21:48:02 UTC
Created attachment 1235743 [details]
File: proc_pid_status

Comment 13 Thanh lam NGUYEN 2016-12-28 21:48:03 UTC
Created attachment 1235744 [details]
File: var_log_messages

Comment 14 Terje Røsten 2017-01-05 18:20:03 UTC
How does /dev/sdc look like? 

What is output (as root) from:

$ fdisk -l /dev/sdc

Comment 15 Thanh lam NGUYEN 2017-01-17 16:38:13 UTC
Hi,sorry for the late response. I didn't check this email account often.
Here is the output:

~ $ fdisk -l /dev/sdc
Disque /dev/sdc : 465,8 GiB, 500107862016 octets, 976773168 secteurs
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 512 octets
taille d'E/S (minimale / optimale) : 512 octets / 512 octets
Type d'étiquette de disque : gpt
Identifiant de disque : D0A8AB0D-86B6-4AAC-AC95-EAA4D400B2C7

Périphérique Début       Fin  Secteurs Taille Type
/dev/sdc1     2048 976773119 976771072 465,8G Système de fichiers Linux

Comment 16 Fedora End Of Life 2017-07-26 00:08:38 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 17 Fedora End Of Life 2017-08-08 19:30:20 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.