[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Dejagnu-commit] [PATCH][Ping v2] Environment variables forwarding

From: Maxim Ostapenko
Subject: [Dejagnu-commit] [PATCH][Ping v2] Environment variables forwarding
Date: Thu, 17 Apr 2014 11:43:09 +0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0


-------- Original Message --------
Subject:        [PATCH][Ping] Environment variables forwarding
Date:   Thu, 03 Apr 2014 17:06:14 +0400
From:   Maxim Ostapenko <address@hidden>
To:     address@hidden
CC: Slava Garbuzov <address@hidden>, Yury Gribov <address@hidden>


-------- Original Message --------
Subject:        Re: [PATCH] Environment variables forwarding
Date:   Mon, 24 Mar 2014 13:46:09 +0400
From:   Maxim Ostapenko <address@hidden>
To:     GCC Patches <address@hidden>, address@hidden
CC:     Yury Gribov <address@hidden>, Slava Garbuzov
<address@hidden>, 'Evgeny Gavrin' <address@hidden>

Adding Dejagnu list this time.

On 03/24/2014 12:28 PM, Maxim Ostapenko wrote:
Hi all,

When porting Lsan on arm, I ran into problem with testing, because
almost all lsan tests require environment variables forwarding for
remote targets. Unfortunately, this feature isn't implemented yet
neither in Dejagnu nor in GCC. These two small patches seem to resolve
this issue.

Tested on arm with asan.exp and ubsan.exp.

I've cross-posted this message in Dejagnu too.

Do these changes make sense? If not - what's the proper way to forward
env vars on remote targets?


Attachment: dejagnu.diff
Description: Text Data

Attachment: gcc_dg.diff
Description: Text Data

reply via email to

[Prev in Thread] Current Thread [Next in Thread]