• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: eclipse debugging help
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: eclipse debugging help


  • Subject: Re: eclipse debugging help
  • From: Florijan Stamenkovic <email@hidden>
  • Date: Wed, 22 Oct 2008 15:22:56 -0400


On Oct 22, 2008, at 14:54, james o'loughlin wrote:

it appears the app deadlocks. my browser hangs and eclipse's debug window opens with the stack i've attached. it does not appear that something is being computed and needs to run its course.

As far as I know Eclipse's debug will auto-open only on breakpoints (exception breakpoints too). Since you could not have put your own breakpoint in the code of NSTimestampFormatter, I assume you have a breakpoint exception setup (you can see that in the "Breakpoints" view in the debugger). If that is so, once the exception breakpoint is hit, you will need to click on the "Resume" button in the "Debug" view. That should let the exception be thrown, which should get it printed out in the console. That should tell you what sort of an exception it is.


If this is really what is happening, then it does not seem to be a deadlock, but Eclipse having suspended your worker thread.

yes, there is an exception being thrown but i can't find the source of this exception. the only feedback i get is the stack window telling me the last piece of my app it talked to was the PageViewer component. from there i'm at a loss.

all of the other threads are (Running).

it's reproducible every time.

the crux is i'm not sure what object is being formatted.

If indeed you are hitting a breakpoint exception, then in the "Variables" view in the debugger (before hitting "Resume") you should have all the current variables visible in the selected stack frame. In short, you should see the object being formatted. Click it, and see what it is.


in the passed, i've found the problem by removing removing HTML from my component until i find the section of code throwing the exception. this is tedious and worse than programming cobol on a vax with a printer... i eventually find the exception but i can't continue this debugging process with any sanity. i'd love for eclipse to point me to the problem.

Yep, Eclipse goes a long way. I suggest googling for eclipse tutorials. I am sure there are free online tutorials out there. And I think I heard that Eclipse's site itself has a decent knowledgeable, but I've never used it so I can't vouch. Rest assured that an hour or two it will require of you will pay off very, very quickly.


F
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >eclipse debugging help (From: james o'loughlin <email@hidden>)
 >Re: eclipse debugging help (From: Florijan Stamenkovic <email@hidden>)
 >Re: eclipse debugging help (From: james o'loughlin <email@hidden>)

  • Prev by Date: Start a WebObject Project
  • Next by Date: Re: Start a WebObject Project
  • Previous by thread: Re: eclipse debugging help
  • Next by thread: Re: Webobjects-dev Digest, Vol 5, Issue 1031
  • Index(es):
    • Date
    • Thread