From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 46999 invoked by alias); 20 Apr 2017 19:54:11 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 46975 invoked by uid 89); 20 Apr 2017 19:54:11 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=serial, Luis, stopped, appreciated! X-HELO: relay1.mentorg.com Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 20 Apr 2017 19:54:08 +0000 Received: from svr-orw-mbx-03.mgc.mentorg.com ([147.34.90.203]) by relay1.mentorg.com with esmtp id 1d1I9Y-0004nu-5j from Luis_Gustavo@mentor.com ; Thu, 20 Apr 2017 12:54:08 -0700 Received: from [172.30.13.156] (147.34.91.1) by svr-orw-mbx-03.mgc.mentorg.com (147.34.90.203) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 20 Apr 2017 12:54:05 -0700 Reply-To: Luis Machado Subject: Re: [PATCH] Make environ.exp run on all platforms (and create info-program.exp) References: <20170331172901.23402-1-sergiodj@redhat.com> <87d1cgtb8a.fsf@redhat.com> <2f1c6f83-5cb0-a1a4-3db2-6b0b9b4b0597@codesourcery.com> <87vaq8rwbm.fsf@redhat.com> To: Sergio Durigan Junior CC: GDB Patches From: Luis Machado Message-ID: <6fb3c3c6-e022-eef4-6638-85cfa39162bc@codesourcery.com> Date: Thu, 20 Apr 2017 19:54:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <87vaq8rwbm.fsf@redhat.com> Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit X-ClientProxiedBy: svr-orw-mbx-03.mgc.mentorg.com (147.34.90.203) To svr-orw-mbx-03.mgc.mentorg.com (147.34.90.203) X-IsSubscribed: yes X-SW-Source: 2017-04/txt/msg00591.txt.bz2 On 04/13/2017 01:34 PM, Sergio Durigan Junior wrote: > On Thursday, April 13 2017, Luis Machado wrote: > >>>> If you don't have access to bare-metal testing, i could give this a >>>> try (it may take a couple days though) and report back. >>> >>> I don't think I have access to a bare-metal easily; if you could test >>> this, I'd really appreciate. >> >> Got it. I'll let you know what i see (likely next week). > > Thanks, much appreciated! > Sorry for the delay. Here it is, for aarch64 bare-metal (both hardware and qemu): -- === gdb Summary === # of expected passes 19 # of unexpected failures 4 Running /gdb/testsuite/gdb.base/info-program.exp ... FAIL: gdb.base/info-program.exp: info program after run to main FAIL: gdb.base/info-program.exp: info program after next FAIL: gdb.base/info-program.exp: info program after deleting all breakpoints Running /gdb/testsuite/gdb.base/environ.exp ... FAIL: gdb.base/environ.exp: show environment works -- The failure for environ.exp seems harmless. I can see the environment variables being printed, but something in the pattern matching is off. I have a number of environment variables, but the matching still fails. I can try to see if there is anything obvious if it doesn't ring any bells for you. For info-program, these failures seem to be related to the "info program" output our remote target provides: -- Breakpoint 1, main (argc=0, argv=0x0) at /gdb/testsuite/gdb.base/normal.c:23^M 23 return 0;^M (gdb) info program^M Debugging a target over a serial line.^M Program stopped at 0x80000a28.^M It stopped at breakpoint 1.^M Type "info stack" or "info registers" for more information.^M (gdb) FAIL: gdb.base/info-program.exp: info program after run to main next^M 24 }^M (gdb) PASS: gdb.base/info-program.exp: advancing pc info program^M Debugging a target over a serial line.^M Program stopped at 0x80000a2c.^M It stopped after being stepped.^M Type "info stack" or "info registers" for more information.^M (gdb) FAIL: gdb.base/info-program.exp: info program after next ... (gdb) info breakpoints^M No breakpoints or watchpoints.^M (gdb) info program^M Debugging a target over a serial line.^M Program stopped at 0x80000a28.^M It stopped at a breakpoint that has since been deleted.^M Type "info stack" or "info registers" for more information.^M (gdb) FAIL: gdb.base/info-program.exp: info program after deleting all breakpoints -- So maybe a matter of making the pattern matching a bit more flexible? Let me know if you want more information.