Description of problem: The following warning is shown, when we run "gcore" command on RHEL4. warning: Memory read failed for corefile section, 16384 bytes at 0x0000000000000000 The warning is not shown, when we run "gcore" command on RHEL3. What should we do to the warning ? Can we have how to aboid to the warning ? Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.ps -ef 2.gcore (PID) -- PID: I selected PID that UID is demon and CMD is "/usr/sbin/atd". Actual results: warning: Memory read failed for corefile section, 16384 bytes at 0x0000000000000000 Expected results: - What should we do to the warning ? - Can we have how to aboid to the warning ? Additional info:
Could you tell me status of this problem ?
We'd like to know status of problem.
Add RHEL4-L3support team in Japan
Bug is being moved to kernel group for assistance. Gdb is getting an error back from reading memory at 00000000-00004000 which is the first entry in the "maps" file for the process. The storage is marked readable but the PTRACE call to read this storage results in an EIO failure as detailed in the strace output I am attaching. I created the result by running the debugger on a simple hello world program, stopping in main, and issuing gcore. For the kernel folks, the failure can be reproduced by running as follows: gcc -g test.c gdb -x t.x a.out I have tried multiple versions of gdb, but they all result in the warning due to the failed PTRACE read.
Created attachment 110165 [details] Sample test used to create strace attachment
Created attachment 110166 [details] Gdb command file used when creating strace output
Created attachment 110167 [details] Strace of gdb running gcore command
Created attachment 110168 [details] Maps file for process that caused problem with gcore
From User-Agent: XML-RPC As the corefile is being created properly without that piece of storage in it, and the message shown is just a warning, and is not actually causing any failure this issue/BZ is being closed as 'not a bug'. If there is some other reason this is causing a problem, please re-open this issue tracker with the appropriate information and details as well as priority. Internal Status set to 'Resolved' Status set to: Closed by Tech Resolution set to: 'NotABug' This event sent from IssueTracker by halligan issue 66082
I have reviewed the patch from Fujitsu. I have modified it only slightly for formatting and have built it into gdb-6.3.0.0-1.13
This has been fixed as of gdb-6.3.0.0-1.14
Customer has confirmed fix.