[PATCH v5 00/14] Fix BZ 25631 - core file memory access problem

Luis Machado luis.machado@linaro.org
Thu Jul 23 10:37:42 GMT 2020


On 7/23/20 12:49 AM, Kevin Buettner wrote:
> On Wed, 22 Jul 2020 19:40:18 -0300
> Luis Machado <luis.machado@linaro.org> wrote:
> 
>> I'm seeing the following regressions on AArch64 Linux running Ubuntu
>> 18.04 (GCC 7).
>>
>> FAIL: gdb.base/corefile.exp: backtrace in corefile.exp
>> FAIL: gdb.base/corefile.exp: core-file warning-free
>> FAIL: gdb.base/corefile.exp: print func2::coremaker_local
>> FAIL: gdb.base/corefile.exp: up in corefile.exp
>> FAIL: gdb.base/corefile.exp: up in corefile.exp (reinit)
>>
>> On a quick look, the test doesn't go according to what is expected.
>>
>> --
>>
>> (gdb) PASS: gdb.base/corefile.exp: print coremaker_ro
>> print func2::coremaker_local^M
>> No frame is currently executing in block func2.^M
>> (gdb) FAIL: gdb.base/corefile.exp: print func2::coremaker_local
>> ...
>> (gdb) PASS: gdb.base/corefile.exp: $_exitcode is void
>> bt^M
>> #0  0x0000ffff80d1c4d8 in raise () from /lib/aarch64-linux-gnu/libc.so.6^M
>> Backtrace stopped: previous frame identical to this frame (corrupt stack?)^M
>> (gdb) FAIL: gdb.base/corefile.exp: backtrace in corefile.exp
>> up^M
>> Initial frame selected; you cannot go up.^M
>> (gdb) FAIL: gdb.base/corefile.exp: up in corefile.exp
>> ...
>> (gdb) file gdb/testsuite/outputs/gdb.base/corefile/corefile^M
>> Load new symbol table from
>> "gdb/testsuite/outputs/gdb.base/corefile/corefile"? (y or n) y^M
>> Reading symbols from gdb/testsuite/outputs/gdb.base/corefile/corefile...^M
>> (gdb) up^M
>> Initial frame selected; you cannot go up.^M
>> (gdb) FAIL: gdb.base/corefile.exp: up in corefile.exp (reinit)
> 
> Hi Luis,
> 
> I'm not seeing these failures on my Raspberry Pi 4 running aarch64
> rawhide.  I have a spare Pi upon which I'll install Ubuntu 18.04.4.
> 
> In the interim, would it be possible for you to show me the same
> sections of the log file from a test run using a GDB build prior to my
> core file patches?

I've attached the complete log files for both runs. Hopefully that will 
be more useful.

Please let me know if you need anything else and I can fetch it.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: corefile_logs.tar.bz2
Type: application/x-bzip
Size: 7999 bytes
Desc: not available
URL: <https://sourceware.org/pipermail/gdb-patches/attachments/20200723/c895044a/attachment-0001.bin>


More information about the Gdb-patches mailing list