Home » Eclipse Projects » Eclipse Platform » Losing my Fricking Mind! (OR - how to get proper debug messages)
| Losing my Fricking Mind! (OR - how to get proper debug messages) [message #249750] |
Fri, 04 June 2004 16:31  |
Eclipse User |
|
|
|
Originally posted by: mark.melvin.dspfactory.com
<The following rant applies to Eclipse 3.0RC1 on Win2K.>
OK - I just spent 1.5 days on a bug I couldn't figure out. My outline
view would not show up for a simple editor using code I cut and pasted
from a working plugin. After inserting breakpoints EVERYWHERE, and
*endless* hours of stepping through the internals of Eclipse making my
eyes glaze over - I had finally decided that I did not want to be a Java
developer anymore. I was just mulling over my new career, mechanically
pressing the 'step over' button when I came across a spot of code that
threw an exception, and lo and behold, examining the output in the
Variables window the toString() method of the exception revealed the
source of my bug. It told me quite clearly that it failed to load
bundle "x.y.x". As it turns out - I made a typo and inserted an extra
's' into the bundle name.
After much gnashing of teeth and gulping of enormous breaths of air to
calm myself down - I find myself wondering how in God's name are you
supposed to debug this beast. I swear on everything I hold dear that
the old 2.1 stream of code would have popped up a nice dialog or at
least printed a message out to the console displaying such a simple
error. Is it just me, or has Eclipse 3.0 (due to OSGI?) seems to have
hidden 90% of this simple stuff. It seems to prefer to simply fail
silently with no indication of what the hell happened. No tracebacks,
no console messages, no dialogs - except for useful ones like:
Save failed.
Reason:
Save failed.
This is like the 3rd or 4th case like this in the past week for me. Is
there some *magical* switch that I don't know about, or do I just have
to get *really* good at knowing where in the innards of Eclipse to
inject my breakpoints? I am running Eclipse with the options "-verbose
-console -debug", and I see no useful output. Someone please tell me I
am missing something simple because I am on the edge of sanity at this
point.
Have a good weekend - I'll still be here... ;o)
Mark.
|
|
|
| Re: Losing my Fricking Mind! (OR - how to get proper debug messages) [message #249753 is a reply to message #249750] |
Fri, 04 June 2004 16:55  |
| Eclipse User |
|
|
|
Originally posted by: paull.NOSPAMcodetelligence.com
It does seem to do a good job of failing ever so silently. It does usually
put a message in the log that is often helpful.
Paul
www.codetelligence.com
"Mark Melvin" <mark.melvin@dspfactory.com> wrote in message
news:c9qlnb$c1b$1@eclipse.org...
> <The following rant applies to Eclipse 3.0RC1 on Win2K.>
>
> OK - I just spent 1.5 days on a bug I couldn't figure out. My outline
> view would not show up for a simple editor using code I cut and pasted
> from a working plugin. After inserting breakpoints EVERYWHERE, and
> *endless* hours of stepping through the internals of Eclipse making my
> eyes glaze over - I had finally decided that I did not want to be a Java
> developer anymore. I was just mulling over my new career, mechanically
> pressing the 'step over' button when I came across a spot of code that
> threw an exception, and lo and behold, examining the output in the
> Variables window the toString() method of the exception revealed the
> source of my bug. It told me quite clearly that it failed to load
> bundle "x.y.x". As it turns out - I made a typo and inserted an extra
> 's' into the bundle name.
>
> After much gnashing of teeth and gulping of enormous breaths of air to
> calm myself down - I find myself wondering how in God's name are you
> supposed to debug this beast. I swear on everything I hold dear that
> the old 2.1 stream of code would have popped up a nice dialog or at
> least printed a message out to the console displaying such a simple
> error. Is it just me, or has Eclipse 3.0 (due to OSGI?) seems to have
> hidden 90% of this simple stuff. It seems to prefer to simply fail
> silently with no indication of what the hell happened. No tracebacks,
> no console messages, no dialogs - except for useful ones like:
>
> Save failed.
> Reason:
> Save failed.
>
> This is like the 3rd or 4th case like this in the past week for me. Is
> there some *magical* switch that I don't know about, or do I just have
> to get *really* good at knowing where in the innards of Eclipse to
> inject my breakpoints? I am running Eclipse with the options "-verbose
> -console -debug", and I see no useful output. Someone please tell me I
> am missing something simple because I am on the edge of sanity at this
> point.
>
> Have a good weekend - I'll still be here... ;o)
> Mark.
|
|
|
| Re: Losing my Fricking Mind! (OR - how to get proper debug messages) [message #249763 is a reply to message #249753] |
Fri, 04 June 2004 17:06 |
| Eclipse User |
|
|
|
Originally posted by: mark.melvin.dspfactory.com
Unfortunately I am testing with only the base runtime and my plugins -
so I don't have the error log view. A good tip however. I can set up
another test install with these activities turned on. Looks like it at
least provides a better starting point.
Thanks for the reply.
Mark.
Paul L wrote:
> It does seem to do a good job of failing ever so silently. It does usually
> put a message in the log that is often helpful.
>
> Paul
> www.codetelligence.com
> "Mark Melvin" <mark.melvin@dspfactory.com> wrote in message
> news:c9qlnb$c1b$1@eclipse.org...
>
>><The following rant applies to Eclipse 3.0RC1 on Win2K.>
>>
>>OK - I just spent 1.5 days on a bug I couldn't figure out. My outline
>>view would not show up for a simple editor using code I cut and pasted
>>from a working plugin. After inserting breakpoints EVERYWHERE, and
>>*endless* hours of stepping through the internals of Eclipse making my
>>eyes glaze over - I had finally decided that I did not want to be a Java
>>developer anymore. I was just mulling over my new career, mechanically
>>pressing the 'step over' button when I came across a spot of code that
>>threw an exception, and lo and behold, examining the output in the
>>Variables window the toString() method of the exception revealed the
>>source of my bug. It told me quite clearly that it failed to load
>>bundle "x.y.x". As it turns out - I made a typo and inserted an extra
>>'s' into the bundle name.
>>
>>After much gnashing of teeth and gulping of enormous breaths of air to
>>calm myself down - I find myself wondering how in God's name are you
>>supposed to debug this beast. I swear on everything I hold dear that
>>the old 2.1 stream of code would have popped up a nice dialog or at
>>least printed a message out to the console displaying such a simple
>>error. Is it just me, or has Eclipse 3.0 (due to OSGI?) seems to have
>>hidden 90% of this simple stuff. It seems to prefer to simply fail
>>silently with no indication of what the hell happened. No tracebacks,
>>no console messages, no dialogs - except for useful ones like:
>>
>>Save failed.
>>Reason:
>>Save failed.
>>
>>This is like the 3rd or 4th case like this in the past week for me. Is
>>there some *magical* switch that I don't know about, or do I just have
>>to get *really* good at knowing where in the innards of Eclipse to
>>inject my breakpoints? I am running Eclipse with the options "-verbose
>>-console -debug", and I see no useful output. Someone please tell me I
>>am missing something simple because I am on the edge of sanity at this
>>point.
>>
>>Have a good weekend - I'll still be here... ;o)
>>Mark.
>
>
>
|
|
|
| Re: Losing my Fricking Mind! (OR - how to get proper debug messages) [message #249801 is a reply to message #249763] |
Fri, 04 June 2004 19:02 |
| Eclipse User |
|
|
|
Mark Melvin wrote:
(snip)
>>> OK - I just spent 1.5 days on a bug I couldn't figure out. My outline
>>> view would not show up for a simple editor using code I cut and pasted
>>> from a working plugin. After inserting breakpoints EVERYWHERE, and
>>> *endless* hours of stepping through the internals of Eclipse making my
>>> eyes glaze over - I had finally decided that I did not want to be a Java
>>> developer anymore. I was just mulling over my new career, mechanically
>>> pressing the 'step over' button when I came across a spot of code that
>>> threw an exception, and lo and behold, examining the output in the
>>> Variables window the toString() method of the exception revealed the
>>> source of my bug. It told me quite clearly that it failed to load
>>> bundle "x.y.x". As it turns out - I made a typo and inserted an extra
>>> 's' into the bundle name.
>>>
>>> After much gnashing of teeth and gulping of enormous breaths of air to
>>> calm myself down - I find myself wondering how in God's name are you
>>> supposed to debug this beast. I swear on everything I hold dear that
>>> the old 2.1 stream of code would have popped up a nice dialog or at
>>> least printed a message out to the console displaying such a simple
>>> error. Is it just me, or has Eclipse 3.0 (due to OSGI?) seems to have
>>> hidden 90% of this simple stuff. It seems to prefer to simply fail
>>> silently with no indication of what the hell happened. No tracebacks,
>>> no console messages, no dialogs - except for useful ones like:
I would recommend another thing that I keep forgetting about. You can
enable LOTS of traces in most of the platform/IDE/etc. plugins.
From the Run... dialog you can clich the Tracing tab for a launch, then
click a few checkboxes. When you launch your program in the runtime
workbench, the console should show a mighty lot of spew.
That is what I did to finally figure out I was calling a deprecated
method that returned a null reference ... etc.
For example, I enabled several of the trace flags for OSGI loading, and
buried in there was a traceback for the NPE that part of the OSGI stuff
had absorbed and rethrown as a ClassNotFoundException.
That traceback pointed directly at *my* code which was doing a nasty thing.
I find the tracing to be more effective than stepping, especially since
there are quite a few places in the runtime that class loading failures
happen as a normal course of events, and exceptions are caught, absorbed
and thrown as other exceptions.
Tom Johnson
|
|
| |
| Re: Losing my Fricking Mind! (OR - how to get proper debug messages) [message #249841 is a reply to message #249763] |
Fri, 04 June 2004 23:33 |
| Eclipse User |
|
|
|
Originally posted by: paull.NOSPAMcodetelligence.com
Do you have enough enabled to have the Help!About Eclipse
Platform!Configuration Details menu enabled? if so, the log is at the bottom
of this display.
Paul
www.codetelligence.com
"Mark Melvin" <mark.melvin@dspfactory.com> wrote in message
news:c9qnpq$e6g$1@eclipse.org...
> Unfortunately I am testing with only the base runtime and my plugins -
> so I don't have the error log view. A good tip however. I can set up
> another test install with these activities turned on. Looks like it at
> least provides a better starting point.
>
> Thanks for the reply.
>
> Mark.
>
> Paul L wrote:
>
> > It does seem to do a good job of failing ever so silently. It does
usually
> > put a message in the log that is often helpful.
> >
> > Paul
> > www.codetelligence.com
> > "Mark Melvin" <mark.melvin@dspfactory.com> wrote in message
> > news:c9qlnb$c1b$1@eclipse.org...
> >
> >><The following rant applies to Eclipse 3.0RC1 on Win2K.>
> >>
> >>OK - I just spent 1.5 days on a bug I couldn't figure out. My outline
> >>view would not show up for a simple editor using code I cut and pasted
> >>from a working plugin. After inserting breakpoints EVERYWHERE, and
> >>*endless* hours of stepping through the internals of Eclipse making my
> >>eyes glaze over - I had finally decided that I did not want to be a Java
> >>developer anymore. I was just mulling over my new career, mechanically
> >>pressing the 'step over' button when I came across a spot of code that
> >>threw an exception, and lo and behold, examining the output in the
> >>Variables window the toString() method of the exception revealed the
> >>source of my bug. It told me quite clearly that it failed to load
> >>bundle "x.y.x". As it turns out - I made a typo and inserted an extra
> >>'s' into the bundle name.
> >>
> >>After much gnashing of teeth and gulping of enormous breaths of air to
> >>calm myself down - I find myself wondering how in God's name are you
> >>supposed to debug this beast. I swear on everything I hold dear that
> >>the old 2.1 stream of code would have popped up a nice dialog or at
> >>least printed a message out to the console displaying such a simple
> >>error. Is it just me, or has Eclipse 3.0 (due to OSGI?) seems to have
> >>hidden 90% of this simple stuff. It seems to prefer to simply fail
> >>silently with no indication of what the hell happened. No tracebacks,
> >>no console messages, no dialogs - except for useful ones like:
> >>
> >>Save failed.
> >>Reason:
> >>Save failed.
> >>
> >>This is like the 3rd or 4th case like this in the past week for me. Is
> >>there some *magical* switch that I don't know about, or do I just have
> >>to get *really* good at knowing where in the innards of Eclipse to
> >>inject my breakpoints? I am running Eclipse with the options "-verbose
> >>-console -debug", and I see no useful output. Someone please tell me I
> >>am missing something simple because I am on the edge of sanity at this
> >>point.
> >>
> >>Have a good weekend - I'll still be here... ;o)
> >>Mark.
> >
> >
> >
|
|
|
| Re: Losing my Fricking Mind! (OR - how to get proper debug messages) [message #250085 is a reply to message #249841] |
Mon, 07 June 2004 09:41 |
| Eclipse User |
|
|
|
Originally posted by: mark.melvin.dspfactory.com
Thanks Tom, Paul, and Ed for the pointers.
Tom - I've never really used traces successfully so I'll check that out
in more detail.
Ed, I have been filing bug reports, but not really enhancement requests.
I'll do more of those.
And Paul - thanks for the log info. I have decided to debug issues like
this with a full SDK runtime instead. The error log still doesn't seem
to point to the specific issue - but it does seem to throw up *some*
error at which point I should be able to dig in a little deeper and see
what the heck is going on.
Fortunately I spent the weekend on my motorcycle and am refreshed and
ready for another week with Eclipse. Serenity NOW! ;o)
Mark.
Paul L wrote:
> Do you have enough enabled to have the Help!About Eclipse
> Platform!Configuration Details menu enabled? if so, the log is at the bottom
> of this display.
>
> Paul
> www.codetelligence.com
> "Mark Melvin" <mark.melvin@dspfactory.com> wrote in message
> news:c9qnpq$e6g$1@eclipse.org...
>
>>Unfortunately I am testing with only the base runtime and my plugins -
>>so I don't have the error log view. A good tip however. I can set up
>>another test install with these activities turned on. Looks like it at
>>least provides a better starting point.
>>
>>Thanks for the reply.
>>
>>Mark.
>>
>>Paul L wrote:
>>
>>
>>>It does seem to do a good job of failing ever so silently. It does
>
> usually
>
>>>put a message in the log that is often helpful.
>>>
>>>Paul
>>>www.codetelligence.com
>>>"Mark Melvin" <mark.melvin@dspfactory.com> wrote in message
>>>news:c9qlnb$c1b$1@eclipse.org...
>>>
>>>
>>>><The following rant applies to Eclipse 3.0RC1 on Win2K.>
>>>>
>>>>OK - I just spent 1.5 days on a bug I couldn't figure out. My outline
>>>>view would not show up for a simple editor using code I cut and pasted
>>>
>>>>from a working plugin. After inserting breakpoints EVERYWHERE, and
>>>
>>>>*endless* hours of stepping through the internals of Eclipse making my
>>>>eyes glaze over - I had finally decided that I did not want to be a Java
>>>>developer anymore. I was just mulling over my new career, mechanically
>>>>pressing the 'step over' button when I came across a spot of code that
>>>>threw an exception, and lo and behold, examining the output in the
>>>>Variables window the toString() method of the exception revealed the
>>>>source of my bug. It told me quite clearly that it failed to load
>>>>bundle "x.y.x". As it turns out - I made a typo and inserted an extra
>>>>'s' into the bundle name.
>>>>
>>>>After much gnashing of teeth and gulping of enormous breaths of air to
>>>>calm myself down - I find myself wondering how in God's name are you
>>>>supposed to debug this beast. I swear on everything I hold dear that
>>>>the old 2.1 stream of code would have popped up a nice dialog or at
>>>>least printed a message out to the console displaying such a simple
>>>>error. Is it just me, or has Eclipse 3.0 (due to OSGI?) seems to have
>>>>hidden 90% of this simple stuff. It seems to prefer to simply fail
>>>>silently with no indication of what the hell happened. No tracebacks,
>>>>no console messages, no dialogs - except for useful ones like:
>>>>
>>>>Save failed.
>>>>Reason:
>>>>Save failed.
>>>>
>>>>This is like the 3rd or 4th case like this in the past week for me. Is
>>>>there some *magical* switch that I don't know about, or do I just have
>>>>to get *really* good at knowing where in the innards of Eclipse to
>>>>inject my breakpoints? I am running Eclipse with the options "-verbose
>>>>-console -debug", and I see no useful output. Someone please tell me I
>>>>am missing something simple because I am on the edge of sanity at this
>>>>point.
>>>>
>>>>Have a good weekend - I'll still be here... ;o)
>>>>Mark.
>>>
>>>
>>>
>
>
|
|
|
Goto Forum:
Current Time: Sun May 11 15:09:32 EDT 2025
Powered by FUDForum. Page generated in 0.03473 seconds |
Home