Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [PING][PATCH][gdb/contrib] cc-with-tweaks.sh: Create .dwz file in .tmp subdir
Date: Fri, 06 Sep 2019 15:28:00 -0000	[thread overview]
Message-ID: <3e167875-f407-2a47-fb3e-74ee7c3d1ece@suse.de> (raw)
In-Reply-To: <20190822144220.GA6937@delia>

On 22-08-19 16:42, Tom de Vries wrote:
> Hi,
> 
> When running a test-case gdb.base/foo.exp with cc-with-dwz-m, a file
> build/gdb/testsuite/outputs/gdb.base/foo/foo.dwz will be created, alongside
> executable build/gdb/testsuite/outputs/gdb.base/foo/foo.
> 
> This can cause problems in f.i. test-cases that test file name completion.
> 
> Make these problems less likely by moving foo.dwz to a .tmp subdir:
> build/gdb/testsuite/outputs/gdb.base/foo/.tmp/foo.dwz.
> 
> Tested on x86_64-linux.
> 
> OK for trunk?

Ping.

Thanks,
- Tom

> [gdb/contrib] cc-with-tweaks.sh: Create .dwz file in .tmp subdir
> 
> gdb/ChangeLog:
> 
> 2019-08-22  Tom de Vries  <tdevries@suse.de>
> 
> 	* contrib/cc-with-tweaks.sh (get_tmpdir): New function.
> 	Use $tmpdir/$(basename "$output_file").dwz instead of
> 	"${output_file}.dwz".
> 
> ---
>  gdb/contrib/cc-with-tweaks.sh | 16 ++++++++++++----
>  1 file changed, 12 insertions(+), 4 deletions(-)
> 
> diff --git a/gdb/contrib/cc-with-tweaks.sh b/gdb/contrib/cc-with-tweaks.sh
> index 7df16bc6c1..98c4f89afc 100755
> --- a/gdb/contrib/cc-with-tweaks.sh
> +++ b/gdb/contrib/cc-with-tweaks.sh
> @@ -163,6 +163,12 @@ then
>      exit 1
>  fi
>  
> +get_tmpdir ()
> +{
> +    tmpdir=$(dirname "$output_file")/.tmp
> +    mkdir -p "$tmpdir"
> +}
> +
>  if [ "$want_objcopy_compress" = true ]; then
>      $OBJCOPY --compress-debug-sections "$output_file"
>      rc=$?
> @@ -202,17 +208,19 @@ if [ "$want_dwz" = true ]; then
>  	;;
>      esac
>  elif [ "$want_multi" = true ]; then
> +    get_tmpdir
> +    dwz_file=$tmpdir/$(basename "$output_file").dwz
>      # Remove the dwz output file if it exists, so we don't mistake it for a
>      # new file in case dwz fails.
> -    rm -f "${output_file}.dwz"
> +    rm -f "$dwz_file"
>  
>      cp $output_file ${output_file}.alt
> -    $DWZ -m ${output_file}.dwz "$output_file" ${output_file}.alt > /dev/null
> +    $DWZ -m "$dwz_file" "$output_file" ${output_file}.alt > /dev/null
>      rm -f ${output_file}.alt
>  
>      # Validate dwz's work by checking if the expected output file exists.
> -    if [ ! -f "${output_file}.dwz" ]; then
> -	echo "$myname: dwz file ${output_file}.dwz missing."
> +    if [ ! -f "$dwz_file" ]; then
> +	echo "$myname: dwz file $dwz_file missing."
>  	exit 1
>      fi
>  fi
> 


  reply	other threads:[~2019-09-06 15:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-22 14:42 [PATCH][gdb/contrib] " Tom de Vries
2019-09-06 15:28 ` Tom de Vries [this message]
2019-09-13 19:50   ` [PING^2][PATCH][gdb/contrib] " Tom de Vries
2019-09-28 20:09 ` [PATCH][gdb/contrib] " Kevin Buettner
2019-09-29 22:01   ` 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=3e167875-f407-2a47-fb3e-74ee7c3d1ece@suse.de \
    --to=tdevries@suse.de \
    --cc=gdb-patches@sourceware.org \
    /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