From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-1.mimecast.com (us-smtp-delivery-1.mimecast.com [207.211.31.120]) by sourceware.org (Postfix) with ESMTP id 0B96A3857C40 for ; Thu, 23 Jul 2020 21:44:59 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 0B96A3857C40 Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-75-cEomcTw6P6mwCakeGdQYEg-1; Thu, 23 Jul 2020 17:44:56 -0400 X-MC-Unique: cEomcTw6P6mwCakeGdQYEg-1 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 6F8A810059A2; Thu, 23 Jul 2020 21:44:55 +0000 (UTC) Received: from f32-m1.lan (ovpn-112-21.phx2.redhat.com [10.3.112.21]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 3E76F73023; Thu, 23 Jul 2020 21:44:54 +0000 (UTC) Date: Thu, 23 Jul 2020 14:44:53 -0700 From: Kevin Buettner To: Luis Machado Cc: gdb-patches@sourceware.org Subject: Re: [PATCH v5 00/14] Fix BZ 25631 - core file memory access problem Message-ID: <20200723144453.4b40d880@f32-m1.lan> In-Reply-To: References: <20200722005832.863276-1-kevinb@redhat.com> <020d4060-b11c-d0d6-4d38-8d26ca07898b@linaro.org> <20200722204927.477ab077@f32-m1.lan> Organization: Red Hat MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-7.8 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Jul 2020 21:45:00 -0000 On Thu, 23 Jul 2020 07:37:42 -0300 Luis Machado wrote: > On 7/23/20 12:49 AM, Kevin Buettner wrote: > > On Wed, 22 Jul 2020 19:40:18 -0300 > > Luis Machado 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. Thanks for sending the log files. One of the things I found puzzling were these messages in after.log: (gdb) core-file /home/user/work/build/binutils-gdb-master/gdb/testsuite/outputs/gdb.base/corefile/corefile.core warning: Can't open file (null) during file-backed mapping note processing warning: Can't open file (null) during file-backed mapping note processing warning: Can't open file (null) during file-backed mapping note processing warning: Can't open file (null) during file-backed mapping note processing warning: Can't open file (null) during file-backed mapping note processing warning: Can't open file (null) during file-backed mapping note processing warning: Can't open file (null) during file-backed mapping note processing Something is going terribly wrong! I've installed Ubuntu 18.04.4 on a Raspberry Pi 3 B+. So far, I haven't been able to reproduce the failures that you're seeing. kev@ubuntu:/ironwood1/sourceware-git/u18.04-rpi3-master/bld/gdb$ cat /etc/issue Ubuntu 18.04.4 LTS \n \l kev@ubuntu:/ironwood1/sourceware-git/u18.04-rpi3-master/bld/gdb$ uname -a Linux ubuntu 5.3.0-1028-raspi2 #30~18.04.2-Ubuntu SMP Fri Jun 19 05:12:46 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux kev@ubuntu:/ironwood1/sourceware-git/u18.04-rpi3-master/bld/gdb$ make check TESTS="gdb.base/corefile.exp" ... === gdb Summary === # of expected passes 30 I'd like to see the following... 1) The output of "uname -a". 2) The output of "cat /etc/issue". 3) The output of "cat /proc/self/coredump_filter". (Is there a better way to know what the global filter is?) 4) The before / after contents of testsuite/outputs/gdb.base/corefile . Thanks, Kevin