public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: "Benoît Thébaudeau" <benoit.thebaudeau@advansee.com>
To: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Cc: crossgcc@sourceware.org
Subject: Re: Broken backtrace
Date: Tue, 13 Dec 2011 20:18:00 -0000	[thread overview]
Message-ID: <f0b21f4c-f4ae-440a-85bd-b48efdd35996@zose-store-12> (raw)
In-Reply-To: <201112132041.43690.yann.morin.1998@anciens.enib.fr>

Yann, all,

> OK, I just understood what happens! Thanks for pointing this.
> Can you try to revert changeset #652e56d6d35a:
>
>     scripts: execute each steps in a subshell
>
>     To avoid variable leakage from one step to another, isolate the
>     steps from each others by running them in their own sub-shell.
>
>     This avoids variables leaking from one step to the others.

That was it: Reverting this changeset works. It removes one subshell
level, and variables are usable in all subshells.

> > Notes regarding CT_OnError() (nothing to do with this issue):
> >  - The step variable (already used in main()) could be defined as
> >  local to be
> > cleaner, even if it does not really matter when exiting.
> >  - "offset=1" seems to be a spurious line.
>
> Probably both right, I'll look after dinner.

Alright.

Best regards,
Benoît Thébaudeau

--
For unsubscribe information see http://sourceware.org/lists.html#faq

  reply	other threads:[~2011-12-13 20:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <64b6c88a-c06e-402d-b3a8-e5b02c39420d@zose-store-12>
2011-12-13 18:05 ` Benoît Thébaudeau
2011-12-13 19:42   ` Yann E. MORIN
2011-12-13 20:18     ` Benoît Thébaudeau [this message]
2011-12-13 23:56       ` Yann E. MORIN

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=f0b21f4c-f4ae-440a-85bd-b48efdd35996@zose-store-12 \
    --to=benoit.thebaudeau@advansee.com \
    --cc=crossgcc@sourceware.org \
    --cc=yann.morin.1998@anciens.enib.fr \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).