From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 55273 invoked by alias); 18 Feb 2020 13:36:54 -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 55262 invoked by uid 89); 18 Feb 2020 13:36:53 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-11.7 required=5.0 tests=AWL,BAYES_00,LIKELY_SPAM_BODY,SPF_PASS autolearn=no version=3.3.1 spammy= X-HELO: mx2.suse.de Received: from mx2.suse.de (HELO mx2.suse.de) (195.135.220.15) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 18 Feb 2020 13:36:52 +0000 Received: from relay2.suse.de (unknown [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id 657C2BA21; Tue, 18 Feb 2020 13:36:50 +0000 (UTC) Subject: Re: [PATCH][gdb/testsuite] Be quiet about untested dtrace-prob.exp To: Luis Machado , gdb-patches@sourceware.org References: <20200218120235.GA9051@delia> <511ae4d0-9d0b-fc77-5ad8-b99f6b0128f6@suse.de> <19291d66-aa9c-6060-3f74-b73dd2e22e6d@linaro.org> From: Tom de Vries Message-ID: <777c391a-9317-65ca-6ddd-7d6756f4b0bc@suse.de> Date: Tue, 18 Feb 2020 13:36:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1 MIME-Version: 1.0 In-Reply-To: <19291d66-aa9c-6060-3f74-b73dd2e22e6d@linaro.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-IsSubscribed: yes X-SW-Source: 2020-02/txt/msg00727.txt.bz2 On 18-02-2020 14:20, Luis Machado wrote: > On 2/18/20 10:13 AM, Tom de Vries wrote: >> On 18-02-2020 13:35, Luis Machado wrote: >>> On 2/18/20 9:02 AM, Tom de Vries wrote: >>>> Hi, >>>> >>>> When running gdb.base/dtrace-probe.exp, I get this on stdout/stderr: >>>> ... >>>> Running src/gdb/testsuite/gdb.base/dtrace-probe.exp ... >>>> gdb compile failed, ld: error in \ >>>>     build/gdb/testsuite/outputs/gdb.base/dtrace-probe/dtrace-probe.o\ >>>>     (.eh_frame); no .eh_frame_hdr table will be created >>>> ld: crt1.o: in function `_start': >>>> start.S:110: undefined reference to `main' >>>> ld: >>>> build/gdb/testsuite/outputs/gdb.base/dtrace-probe/dtrace-probe-p.o:\ >>>>     (.SUNW_dof+0x88): undefined reference to `main' >>>> ld: >>>> build/gdb/testsuite/outputs/gdb.base/dtrace-probe/dtrace-probe-p.o:\ >>>>     (.SUNW_dof+0xb8): undefined reference to `main' >>>> collect2: error: ld returned 1 exit status >>>> >>>>                   === gdb Summary === >>>> >>>> nr of untested testcases         1 >>> >>> Odd. I'm running this natively on aarch64 and i don't see the same. I >>> only get output in gdb.log. >>> >> >> I've looked a bit at the semantics of output_clone (in >> /usr/share/dejagnu/framework.exp), and the only way I could think of how >> that would happen for you is if the output somehow starts with a keyword >> like PASS/FAIL/WARNING/ERROR/etc. [ If you want to chase that difference >> it could be useful to post a gdb.log/gdb.sum/stdout_stderr.log. ] > > I think the setup i have differs from yours. I don't have DTtrace, so > the testsuite ends up using pdtrace. Same here. > That somehow makes things go a > different way. The build ends up failing, but silently. > > as: unrecognized option '-64 > readelf: Error: > 'binutils-gdb-master/gdb/testsuite/outputs/gdb.base/dtrace-probe/dtrace-probe-p.o': > No such file > error: could not extract the start of shdr from > binutils-gdb-master/gdb/testsuite/outputs/gdb.base/dtrace-probe/dtrace-probe-p.o > > UNTESTED: gdb.base/dtrace-probe.exp: failed to compile OK, that explains it. In both cases, dtrace_build_usdt_test_program fails, in my case in a gdb_compile call, in your case in one of the $dtrace calls (my guess is the second one). Thanks, - Tom