Oh .. crap -- I mean kill -QUIT ... kill -QUIT sends a quit signal to
the VM and tells it to dump the active thread stacks. It will not
kill the app, just dump stack traces.
On Nov 15, 2007, at 3:38 PM, Lachlan Deck wrote:
> kill -HUP didn't kill it. Had to kill -INT... no stack traces :-/
>
> On 16/11/2007, at 7:28 AM, Mike Schrag wrote:
>
>> There aren't any that I know of, but that doesn't mean anything ...
>> You should be able to kill -HUP the eclipse process and it will
>> dump all the threads stack traces either to console or to the .log
>> file.
>>
>> ms
>>
>> On Nov 15, 2007, at 3:17 PM, Lachlan Deck wrote:
>>
>>> Hi there,
>>>
>>> are there any known race conditions in Entity Modeler like
>>> clicking on an entity too early (whilst the view is opening) that
>>> triggers the spinning beach ball of death?
>>>
>>> I've just re-opened a model that has a single entity - but related
>>> to another model (in a differing framework) and I'm twiddling my
>>> thumbs.
>>>
>>> Any ideas? Any way I can get a stack trace while its stuck?
>>>
>>> with regards,
>>> --
>>>
>>> Lachlan Deck
>>>
>>>
>>>
>>
>>
>
> with regards,
> --
>
> Lachlan Deck
>
>
>
This archive was generated by hypermail 2.0.0 : Thu Nov 15 2007 - 15:49:42 EST