Hi James,
This looks like a bug. Feel free to file it.
Adam
On Thu, Nov 08, 2007 at 04:41:21PM -0800, James McIlree wrote:
>
> Does anyone know why these scripts behave differently?
>
> It looks to me like the thread local variable is being treated as
> un-initialized, or a pointer
On Wed, 2007-11-07 at 21:52 -0500, Rayson Ho wrote:
> Roman,
>
> Since you are on the Sun Studio team, and since this thread is related
> to threads/locks, may be it is a good place to ask here...
>
> Intel has thread checker, which is similar to Sun's thread analyzer.
> However, is there a tool
Does anyone know why these scripts behave differently?
It looks to me like the thread local variable is being treated as
un-initialized, or a pointer without backing store.
Is this intentional?
James M
# cat global.d
struct foo { int a; };
struct foo ttest;
BEG
JDK-1.6.0_03-b05 (that's JDK 6, update 3 build 5) has all the
changes I know of for recent Intel chips.
I'm going to hope that the DTrace folks can figure this one
out. If they need help on the Java side of things I can help.
... peter
Naveen Nalam wrote:
>> Which versi
