Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Strasuns, Mihails" <mihails.strasuns@intel.com>
To: Simon Marchi <simon.marchi@polymtl.ca>,
	Tom de Vries <tdevries@suse.de>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [committed][gdb/testsuite] Fix incorrect string concat in jit-elf.exp
Date: Tue, 12 May 2020 14:37:09 +0000	[thread overview]
Message-ID: <MWHPR11MB0048F64C6FC7C0D5503C215B95BE0@MWHPR11MB0048.namprd11.prod.outlook.com> (raw)
In-Reply-To: <73a5e27b-a709-8861-1f88-a07a0a2a71f9@polymtl.ca>

On that topic - what is the recommended set of boards to check locally for a generic gdb patchset?

Mihails

> -----Original Message-----
> From: Simon Marchi <simon.marchi@polymtl.ca>
> Sent: Tuesday, May 12, 2020 4:15 PM
> To: Tom de Vries <tdevries@suse.de>; gdb-patches@sourceware.org
> Cc: Strasuns, Mihails <mihails.strasuns@intel.com>
> Subject: Re: [committed][gdb/testsuite] Fix incorrect string concat in jit-
> elf.exp
> 
> On 2020-05-12 9:00 a.m., Tom de Vries wrote:
> > Hi,
> >
> > When running test-case gdb.base/jit-elf.exp with target board
> > cc-with-gdb-index, we get:
> > ...
> > spawn -ignore SIGHUP gdb/contrib/cc-with-tweaks.sh -i gcc \
> >   -fno-stack-protector src/gdb/testsuite/gdb.base/jit-elf-main.c \
> >   -fdiagnostics-color=never -DATTACH=1 -DLOAD_ADDRESS=0x7000000 \
> >   -DLOAD_INCREMENT=0x1000000 -g -lm \
> >   -o outputs/gdb.base/jit-elf/jit-elf-main"-attach"^M
> > outputs/gdb.base/jit-elf/.tmp/jit-elf-main-attach: \
> >   No such file or directory.^M
> > output is:
> > outputs/gdb.base/jit-elf/.tmp/jit-elf-main-attach: \
> >   No such file or directory.^M
> >
> > gdb compile failed, outputs/gdb.base/jit-elf/.tmp/jit-elf-main-attach: \
> >   No such file or directory.
> > UNTESTED: gdb.base/jit-elf.exp: failed to compile jit-elf-main"-attach"
> > ...
> >
> > The problem is a string concat in jit-elf.exp:
> > ...
> >   ${main_binfile}"-attach"
> > ...
> > which is intended to generate string 'jit-elf-main-attach' but instead
> > generates string 'jit-elf-main"-attach"'.
> >
> > Fix this by using "${main_binfile}-attach" instead.
> >
> > Tested on x86_64-linux.
> >
> > Committed to trunk.
> >
> > Thanks,
> > - Tom
> 
> Thanks for the fixes to the JIT tests Tom.  I did not test with non-default
> boards, I'll try to do it more diligently in the future.
> 
> Simon
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Gary Kershaw
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928

  reply	other threads:[~2020-05-12 14:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-12 13:00 Tom de Vries
2020-05-12 14:14 ` Simon Marchi
2020-05-12 14:37   ` Strasuns, Mihails [this message]
2020-05-13  8:52     ` Tom de Vries
2020-05-13 13:45       ` Simon Marchi
2020-05-26  8:49         ` How to run multiple target boards Tom de Vries
2020-05-26 10:39           ` Pedro Alves
2020-05-26 10:56             ` Tom de Vries
2020-05-26 20:38               ` Simon Marchi
2020-05-13  8:44   ` [committed][gdb/testsuite] Fix incorrect string concat in jit-elf.exp Tom de Vries

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=MWHPR11MB0048F64C6FC7C0D5503C215B95BE0@MWHPR11MB0048.namprd11.prod.outlook.com \
    --to=mihails.strasuns@intel.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@polymtl.ca \
    --cc=tdevries@suse.de \
    /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