From: Luis Machado <luis.machado@linaro.org>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v5 00/14] Fix BZ 25631 - core file memory access problem
Date: Thu, 23 Jul 2020 07:37:42 -0300 [thread overview]
Message-ID: <ee28384a-0339-1962-f044-f693e9539a43@linaro.org> (raw)
In-Reply-To: <20200722204927.477ab077@f32-m1.lan>
[-- Attachment #1: Type: text/plain, Size: 2063 bytes --]
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.
[-- Attachment #2: corefile_logs.tar.bz2 --]
[-- Type: application/x-bzip, Size: 7999 bytes --]
next prev parent reply other threads:[~2020-07-23 10:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 0:58 Kevin Buettner
2020-07-22 0:58 ` [PATCH v5 01/14] Remove hack for GDB which sets the section size to 0 Kevin Buettner
2020-07-22 0:58 ` [PATCH v5 02/14] Adjust corefile.exp test to show regression after bfd hack removal Kevin Buettner
2020-07-22 0:58 ` [PATCH v5 03/14] section_table_xfer_memory: Replace section name with callback predicate Kevin Buettner
2020-07-22 0:58 ` [PATCH v5 04/14] Provide access to non SEC_HAS_CONTENTS core file sections Kevin Buettner
2020-07-22 0:58 ` [PATCH v5 05/14] Test ability to access unwritten-to mmap data in core file Kevin Buettner
2020-07-22 0:58 ` [PATCH v5 06/14] Update binary_get_section_contents to seek using section's file position Kevin Buettner
2020-07-22 0:58 ` [PATCH v5 07/14] Add new gdbarch method, read_core_file_mappings Kevin Buettner
2020-07-22 0:58 ` [PATCH v5 08/14] Use NT_FILE note section for reading core target memory Kevin Buettner
2020-07-22 0:58 ` [PATCH v5 09/14] Add test for accessing read-only mmapped data in a core file Kevin Buettner
2020-07-22 0:58 ` [PATCH v5 10/14] gcore command: Place all file-backed mappings in NT_FILE note Kevin Buettner
2020-07-22 0:58 ` [PATCH v5 11/14] Adjust coredump-filter.exp to account for NT_FILE note handling Kevin Buettner
2020-07-22 18:56 ` Pedro Alves
2020-07-22 0:58 ` [PATCH v5 12/14] Add new command "maint print core-file-backed-mappings" Kevin Buettner
2020-07-23 13:08 ` Tom de Vries
2020-07-23 20:47 ` Kevin Buettner
2020-07-22 0:58 ` [PATCH v5 13/14] Add documentation for " Kevin Buettner
2020-07-22 2:27 ` Eli Zaretskii
2020-07-22 0:58 ` [PATCH v5 14/14] New core file tests with mappings over existing program memory Kevin Buettner
2020-07-22 18:58 ` [PATCH v5 00/14] Fix BZ 25631 - core file memory access problem Pedro Alves
2020-07-22 20:14 ` Kevin Buettner
2020-07-22 22:40 ` Luis Machado
2020-07-23 3:49 ` Kevin Buettner
2020-07-23 10:37 ` Luis Machado [this message]
2020-07-23 21:44 ` Kevin Buettner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ee28384a-0339-1962-f044-f693e9539a43@linaro.org \
--to=luis.machado@linaro.org \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox