Re: MemberName$Factory.resolve() and the Eclipse debugger.

2014-11-18 Thread Marcus Lagergren
Nicely done, Duncan. Do you have a link to the issue report? Regards Marcus On 03 Nov 2014, at 16:48, MacGregor, Duncan (GE Energy Management) duncan.macgre...@ge.com wrote: I’ve reported an Eclipse bug. Doesn’t look like their debugger has ever done quite the right thing, unless the

Re: MemberName$Factory.resolve() and the Eclipse debugger.

2014-11-18 Thread MacGregor, Duncan (GE Energy Management)
https://bugs.eclipse.org/bugs/show_bug.cgi?id=449791 On 18/11/2014 14:06, Marcus Lagergren marcus.lagerg...@oracle.com wrote: Nicely done, Duncan. Do you have a link to the issue report? Regards Marcus On 03 Nov 2014, at 16:48, MacGregor, Duncan (GE Energy Management) duncan.macgre...@ge.com

Re: MemberName$Factory.resolve() and the Eclipse debugger.

2014-11-18 Thread George Marrows
Does anyone here know the best way to engage with the Eclipse developers on this kind of thing? We will try their mailing list ( http://dev.eclipse.org/mhonarc/lists/jdt-debug-dev/), but it's eerily quiet George On Tue, Nov 18, 2014 at 3:29 PM, MacGregor, Duncan (GE Energy Management)

Re: MemberName$Factory.resolve() and the Eclipse debugger.

2014-11-03 Thread MacGregor, Duncan (GE Energy Management)
I’ve reported an Eclipse bug. Doesn’t look like their debugger has ever done quite the right thing, unless the behaviour of the JVM has changed significantly. On 03/11/2014 15:33, Christian Thalinger christian.thalin...@oracle.com wrote: Interesting. Thanks for digging deep. On Oct 31, 2014,

Re: MemberName$Factory.resolve() and the Eclipse debugger.

2014-10-31 Thread MacGregor, Duncan (GE Energy Management)
Okay, I now know why the JVM is stuck for so long, just not why Eclipse is doing what it does. At certain points during the loading of our application Eclipse will make a large number (upto 1) jdwp classesForSignature requests, each of which causes the jdwp lib to trawl over a large number of

MemberName$Factory.resolve() and the Eclipse debugger.

2014-10-29 Thread MacGregor, Duncan (GE Energy Management)
When we’ve tried to debug some of our Java core in the context of running a large application we’ve been seeing long pauses (sometime very long pauses of over a minute) due to java.lang.invoke.MemberName$Factory.resolve() apparently taking ages to complete. Testing with an openjdk build I see

Re: MemberName$Factory.resolve() and the Eclipse debugger.

2014-10-29 Thread Christian Thalinger
On Oct 29, 2014, at 9:39 AM, MacGregor, Duncan (GE Energy Management) duncan.macgre...@ge.com wrote: When we’ve tried to debug some of our Java core in the context of running a large application we’ve been seeing long pauses (sometime very long pauses of over a minute) due to

Re: MemberName$Factory.resolve() and the Eclipse debugger.

2014-10-29 Thread MacGregor, Duncan (GE Energy Management)
On 29/10/2014 16:55, Christian Thalinger christian.thalin...@oracle.com wrote: On Oct 29, 2014, at 9:39 AM, MacGregor, Duncan (GE Energy Management) duncan.macgre...@ge.com wrote: When we¹ve tried to debug some of our Java core in the context of running a large application we¹ve been seeing

Re: MemberName$Factory.resolve() and the Eclipse debugger.

2014-10-29 Thread Christian Thalinger
On Oct 29, 2014, at 10:06 AM, MacGregor, Duncan (GE Energy Management) duncan.macgre...@ge.com wrote: On 29/10/2014 16:55, Christian Thalinger christian.thalin...@oracle.com wrote: On Oct 29, 2014, at 9:39 AM, MacGregor, Duncan (GE Energy Management) duncan.macgre...@ge.com wrote:

Re: MemberName$Factory.resolve() and the Eclipse debugger.

2014-10-29 Thread MacGregor, Duncan (GE Energy Management)
On 29/10/2014 17:13, Christian Thalinger christian.thalin...@oracle.com wrote: On Oct 29, 2014, at 10:06 AM, MacGregor, Duncan (GE Energy Management) duncan.macgre...@ge.com wrote: On 29/10/2014 16:55, Christian Thalinger christian.thalin...@oracle.com wrote: On Oct 29, 2014, at 9:39 AM,