Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Indigo Testing - How to report when Eclipse becomes unresponsive

Just to follow up I think I was able to get a Java thread dump instead of the native thread dump that I posted to the bug yesterday. I attached it to the bug report that I submitted yesterday. https://bugs.eclipse.org/bugs/show_bug.cgi?id=345970  Thanks to all who helped me get the information needed for the bug.
--
Mike Jackson <www.bluequartz.net>

On May 17, 2011, at 2:26 AM, Schorn, Markus wrote:

> Hi,
> In many cases a thread-dump, taken at the point in time, where the IDE is stuck, can give the initial hint on what causes the delays.
> See http://wiki.eclipse.org/How_to_report_a_deadlock for details on how to create a thread dump.
> Markus.
> 
> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Michael Jackson
> Sent: Montag, 16. Mai 2011 17:17
> To: CDT General developers list.
> Subject: [cdt-dev] Indigo Testing - How to report when Eclipse becomes unresponsive
> Importance: Low
> 
> I pulled Indigo M7 and have been applying the CDT RC's as they become available. periodically Eclipse becomes unresponsive and I have to force quit it and then relaunch it. I am on OS X 10.6.8 with the Indigo M7 Cocoa x64 version running. Now that I think about it, I have the same issue with Helios and I switched to the 32 Bit Carbon version and the lock ups have seemed to go away. 
>  The real question: When these lock ups occur, how can I help "us" figure out what is causing the issues? Are there log files, or backtraces or something that I can provide that might help provide insight into the bug that is happening? 
> 
> The hardware is a 2009 Mac Pro, SSD as boot drive and 12GB Ram and I am running all the latest updates/security patches from Apple.
> 
> I searched the Eclipse Bug database and didn't seem to find anything that matches that has NOT been marked as resolved.
> 
> Thanks.
> ___________________________________________________________
> Mike Jackson                      www.bluequartz.net
> Principal Software Engineer       mike.jackson@xxxxxxxxxxxxxx 
> BlueQuartz Software               Dayton, Ohio
> 



Back to the top