Displaying 4 results from an estimated 4 matches for "l1072".
Did you mean:
1072
2017 Jun 06
4
LLD support for ld64 mach-o linker synthesised symbols
...r **argv, char **envp, char **applep)
{
for (__init_fn *p = &__init_start; p < &__init_end; ++p) {
(*p)(argc, argv, envp, applep);
}
}
Michael.
[1] https://github.com/opensource-apple/xnu/blob/dc0628e187c3148723505cf1f1d35bb948d3195b/bsd/kern/kern_exec.c#L1072-L1111 <https://github.com/opensource-apple/xnu/blob/dc0628e187c3148723505cf1f1d35bb948d3195b/bsd/kern/kern_exec.c#L1072-L1111>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170607/eb534f68/attachment....
2017 Jun 06
2
LLD support for ld64 mach-o linker synthesised symbols
...> for (__init_fn *p = &__init_start; p < &__init_end; ++p) {
> (*p)(argc, argv, envp, applep);
> }
> }
>
> Michael.
>
> [1] https://github.com/opensource-apple/xnu/blob/dc0628e187c3148723505cf1f1d35bb948d3195b/bsd/kern/kern_exec.c#L1072-L1111 <https://github.com/opensource-apple/xnu/blob/dc0628e187c3148723505cf1f1d35bb948d3195b/bsd/kern/kern_exec.c#L1072-L1111>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>
>...
2017 Jun 07
3
LLD support for ld64 mach-o linker synthesised symbols
...start; p < &__init_end; ++p) {
>> (*p)(argc, argv, envp, applep);
>> }
>> }
>>
>>
>> Michael.
>>
>> [1] https://github.com/opensource-apple/xnu/blob/dc0628e187c
>> 3148723505cf1f1d35bb948d3195b/bsd/kern/kern_exec.c#L1072-L1111
>>
>> _______________________________________________
>> LLVM Developers mailing list
>> llvm-dev at lists.llvm.org
>> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>>
>>
>
>
>
> _______________________________________________
&g...
2020 Jan 11
7
Why are the arguments supplied for the command run through ssh interpreted by shell before they are passed to the command on the server side?
On 2020-01-11 01:38, Darren Tucker wrote:
> The command you give is always handled on the server by your shell in some
> fashion. It has to be, because SSH only specifies an opaque string for the
> remote command, so without doing so you would not be able to specify
> arguments at all.
It's not obvious why does it have to be this way. ssh sends the command
as an array of