Debugging the GMF generator [message #113774] |
Thu, 22 March 2007 11:39  |
Eclipse User |
|
|
|
Originally posted by: andrew.montalenti.morganstanley.com
I am currently evaluating GMF for use in building a graphical modeling
tool. I am working with the latest stable stream build (3.3M5) of
Eclipse, GMF 2.0M5uh and its dependencies.
I am running into situations in which certain .gmfmap files cause
NullPointerExceptions inside the GMF generator. I can see the stack
traces for these NPEs in my Eclipse log, but cannot find an easy way to
"debug" these problems so I can step through the code and see exactly
what's going wrong. I'd ultimately like to file informative bug reports
about these problems so that more informative error messages may be
logged, and less scary exceptions thrown.
The issue is that I'd like to debug my running Eclipse instance (that is,
set a breakpoint in the GMF generator, and have the debugger come up when
I click the "Generate Diagram Code" menu action). Is there any way to do
this?
Alternatively, is there some way, without creating a plug-in project which
depends upon the GMF generator, that I could use an Eclipse Application
launcher to start another instance of Eclipse where I could debug the
generator? I've searched through all the views for the Plug-In Registry,
etc. with little luck.
This is certainly more of a general Eclipse question, but I am asking it
here because I figure some GMF users/devs must have to do stuff like this
sometimes in order to get to the root of GMF problems.
Thanks for any help or pointers,
Andrew
|
|
|
|
|
Re: Debugging the GMF generator [message #114439 is a reply to message #114111] |
Mon, 26 March 2007 12:13  |
Eclipse User |
|
|
|
Originally posted by: andrew.montalenti.morganstanley.com
Hi Alex,
I realized that I was running a somewhat older build of GMF (due to an
overzealous use of update sites). I upgraded to the latest 2.0M5 build
and this bug went away.
At the end of the day, I think it was related to using spaces in the name
of something (like a Figure). If I encounter the error again, I'll post
the stack trace here.
Andrew
|
|
|
Powered by
FUDForum. Page generated in 0.03340 seconds