Displaying 5 results from an estimated 5 matches for "64435".
Did you mean:
6443
2015 Sep 25
2
Dynamic VMA in Sanitizers for AArch64
...anitizer internals IMNSHO, all that is needed is to make runtime
> decisions during libasan initialization on the memory layout, and
> also (because 39 bit VMA is too slow), dynamic decision whether to use
> 32-bit or 64-bit allocator. See
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64435
> for details.
Added kcc.
FYI optional dynamic offset would also help in not-so-rare situations
when ASan's shadow range is stolen by early constructors in unsanitized
libraries.
-Y
2015 Sep 25
3
Dynamic VMA in Sanitizers for AArch64
Hi folks,
After long talks with lots of people, I think we have a winning
strategy to deal with the variable nature of VMA address in AArch64.
It seems that the best way forward is to try the dynamic calculation
at runtime, evaluate the performance, and then, only if the hit is too
great, think about compile-time alternatives. I'd like to know if
everyone is in agreement, so we could get
2015 Sep 25
2
Dynamic VMA in Sanitizers for AArch64
...hat is needed is to make runtime
>>> decisions during libasan initialization on the memory layout, and
>>> also (because 39 bit VMA is too slow), dynamic decision whether to use
>>> 32-bit or 64-bit allocator. See
>>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64435
>>> for details.
>>
>>
>> Added kcc.
>>
>> FYI optional dynamic offset would also help in not-so-rare situations
>> when ASan's shadow range is stolen by early constructors in unsanitized
>> libraries.
>
>
> And - we'll finally be...
2008 Aug 25
11
pid-provider sees ld.so.1 only
I''m trying to do some userspace tracing on a server-process with the pid provider.
My problem is, that the only probes the pid-provider lists for the server-process (to which I attach dtrace with "-p nnnn") are coming from "ld.so.1".
There''s not a single one from my modules.
If I''m specifying "a.out" (or any of our shared-objects) as the
2010 Jul 13
3
Problem mapping Samba shares in Windows
Hi,
In our company we are currently running a Samba server and Windows XP clients.
At the moment we are having problems with mapping Samba shares in Windows.
Shares are being mapped through a windows startup script, which executes net use (with the option persistent:no) command.
For most users this works most of the time, nevertheless it often fails, the exect reason for this isn't clear