Displaying 4 results from an estimated 4 matches for "shra".
Did you mean:
shr
2003 Aug 03
2
Weird permission problem
Hi,
When I try to do anything on my samba system a connection is made to IPC$, but this is
mapped to a directory /root/tmp. This seems odd. To make matters worse ordinary users
cannot access this directory, so the only user who can access the IPC$ share (ie, do
anything at all) is the root user.
What have I don wrong. I cannot find any reference to IPC$ being linked to a directory
2007 Apr 17
1
updating textmate bundle
Just to let you know - in the textmate bundle the snippet shra =>
"Should raise error" is missing an open parenthesis. The snippet
code should be this:
lambda { $1 }.should raise_error(${2:error})
$0
and not this:
lambda { $1 }.should raise_error${2:error})
$0
Best,
Scott
2016 Feb 08
2
[LLD] Incorrect comparision of pointers to function defined in DSO
...T
> entry. After all, that is address to which a call to the function will jump.
> However, each shared library has its own PLT, and thus the address of a
> particular function would differ in each shared library. That means that
> comparisons of function pointers generated in different shraed libraries may
> be different when they should be the same. This is not a purely hypothetical
> problem; when I did a port which got it wrong, before I fixed the bug I saw
> failures in the Tcl shared library when it compared function pointers.
>
> The fix for this bug on most proce...
2016 Feb 08
3
[LLD] Incorrect comparision of pointers to function defined in DSO
Hi,
It looks like I have found a bug in LLD. Suppose DSO defines a global
variable 'data' and initializes it by the address of function
'set_data' defined in the same DSO. If an executable file (linked by
LLD) gets address of the '&set_data' function and compares it with a
value stored in the 'data' variable it gets different result. If the
executable is linked