Bug 14632 - gcore or gdb create invalid core dump
Summary: gcore or gdb create invalid core dump
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2014-11-21 10:54 CET by Nikita Krupenko
Modified: 2017-09-10 20:28 CEST (History)
1 user (show)

See Also:
Source RPM: gdb-7.8-6.mga5
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Nikita Krupenko 2014-11-21 10:54:17 CET 
Trying to get core dump with gcore I see the following messages:

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
0x00007fdcc136be03 in __select_nocancel () from /lib64/libc.so.6
warning: target file /proc/4405/cmdline contained unexpected null characters
warning: Memory read failed for corefile section, 8192 bytes at 0x7fff153f7000.
Saved corefile core.4405

It creates core dump but not properly and it not works with some debuggers.

On CentOS 6.5 with gdb 7.2-64.el6_5.2 I have no this problem.
David Walser 2014-11-21 22:32:11 CET

Assignee: bugsquad => thierry.vignaud

Comment 1 Thierry Vignaud 2014-11-21 23:32:55 CET 
Please try with 7.8.1-1.mga5
Thierry Vignaud 2014-11-21 23:33:07 CET

Keywords: (none) => NEEDINFO

Comment 2 Nikita Krupenko 2014-11-24 15:59:38 CET 
Tried, same errors.
Comment 3 Samuel Verschelde 2015-05-19 14:10:40 CEST 
Is the bug still present in latest cauldron?
Comment 4 Marja Van Waes 2017-09-10 20:28:19 CEST 
(In reply to Samuel Verschelde from comment #3)
> Is the bug still present in latest cauldron?



Since we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

CC: (none) => marja11
Resolution: (none) => OLD
Status: NEW => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.