Hi,
On 18/11/14 16:39, Mateusz Kowalczyk wrote:
> As long as it's optional: debugging wrappers does happen and if it's
> binary then there's no hope.
Of course there is: a wrapper just sets some environment variables before
calling another program, so you can see its effect by doing "strace -eex
On 11/18/2014 01:32 PM, Wout Mertens wrote:
> Hi all,
>
> I'm wondering if it wouldn't be better to make the application wrapper
> scripts generated by makeWrapper be binaries that do the environment
> massaging and config in binary code before exec() ing the wrapped program.
>
> The advantages w
Some time ago I had an idea for a ‘wrapper interpreter’, seems like execline
might be similar. No reason we can’t have such a thing.
> On Nov 18, 2014, at 9:02 AM, Thomas Tuegel wrote:
>
> On Tue, Nov 18, 2014 at 7:32 AM, Wout Mertens wrote:
>> Hi all,
>>
>> I'm wondering if it wouldn't be be
On Tue, Nov 18, 2014 at 7:32 AM, Wout Mertens wrote:
> Hi all,
>
> I'm wondering if it wouldn't be better to make the application wrapper
> scripts generated by makeWrapper be binaries that do the environment
> massaging and config in binary code before exec() ing the wrapped program.
>
> The adva
Hi all,
I'm wondering if it wouldn't be better to make the application wrapper
scripts generated by makeWrapper be binaries that do the environment
massaging and config in binary code before exec() ing the wrapped program.
The advantages would be that the wrapper itself loads very fast since all
