Home » Language IDEs » C / C++ IDE (CDT) » Newbie Questions
| Newbie Questions [message #24491] |
Tue, 16 April 2002 19:42  |
Eclipse User |
|
|
|
Hi -
I am familiar with Eclipse but new to CDT, and I have been trying to
dive into the code. I have two questions regarding CDT that any of the
CDT developers could probably answer pretty quickly.
First, I am having problems rebuilding the com.ibm.debug plugin with the
source zips from CDT build 20020408. I am using the latest stable
Eclipse build, from 20020321. I imported all of the CDT plugins (and
their dependencies) to a workspace, and added the necessary plugins to
the Projects tab under the Build Path property. When I try to rebuild
com.ibm.debug I get errors about missing PICLDebugPlugin. Although
there appears to be a PICLDebugPlugin.class in the included ibmdebug.jar
file, there is no Java file to compile a new one. My only other idea is
that the plugin.xml mentions PICLDebugPlugin as the class associated
with the com.ibm.debug plugin. Any suggestions on how to rebuild this
plugin would be appreciated.
Secondly, I was curious about the best way to go about
exploring/debugging the GdbPicl from within an Eclipse workspace. It
seems to not technically be a plugin, as it has no plugin.xml. The only
thing I have come up with so far is to import the src zips for the Picl,
and replace the jar file manually in the eclipse/plugins directory after
recompiling. Is there an easier way? Any suggestions on this would be
a great help!
Thanks everybody-
John
|
|
|
| Re: Newbie Questions [message #24572 is a reply to message #24491] |
Wed, 17 April 2002 08:51  |
| Eclipse User |
|
|
|
Hi John,
The 20020408 contains a debugger that apparently has a source zip that it is
out of synch with the generated jars. We actually pick up the debugger (and
LPEX editor) from other teams that perform their own builds and provide us
with exactly what you see. The fact that you (and we) can't build from the
source provided is definitely a problem and I am looking into fixing it.
The ideal way IMHO to fix it, is to unify the build process so that the
entire build of all the CDT components is done from source residing in our
CVS. That way we can verify the packaging of the source and be responsive
to problems like this. I will post a reply to this message when I make
some progress.
<johnrose@austin.ibm.com> wrote in message
news:3CBCB6EA.AEF72BAA@austin.ibm.com...
> Hi -
>
> I am familiar with Eclipse but new to CDT, and I have been trying to
> dive into the code. I have two questions regarding CDT that any of the
> CDT developers could probably answer pretty quickly.
>
> First, I am having problems rebuilding the com.ibm.debug plugin with the
> source zips from CDT build 20020408. I am using the latest stable
> Eclipse build, from 20020321. I imported all of the CDT plugins (and
> their dependencies) to a workspace, and added the necessary plugins to
> the Projects tab under the Build Path property. When I try to rebuild
> com.ibm.debug I get errors about missing PICLDebugPlugin. Although
> there appears to be a PICLDebugPlugin.class in the included ibmdebug.jar
> file, there is no Java file to compile a new one. My only other idea is
> that the plugin.xml mentions PICLDebugPlugin as the class associated
> with the com.ibm.debug plugin. Any suggestions on how to rebuild this
> plugin would be appreciated.
>
> Secondly, I was curious about the best way to go about
> exploring/debugging the GdbPicl from within an Eclipse workspace. It
> seems to not technically be a plugin, as it has no plugin.xml. The only
> thing I have come up with so far is to import the src zips for the Picl,
> and replace the jar file manually in the eclipse/plugins directory after
> recompiling. Is there an easier way? Any suggestions on this would be
> a great help!
>
> Thanks everybody-
> John
>
|
|
|
| Re: Newbie Questions [message #24654 is a reply to message #24491] |
Wed, 17 April 2002 14:18 |
| Eclipse User |
|
|
|
Hi John,
You are right that GDBPicl is not a real plugin. It is a java application
that helps integrate native GDB debugger with Eclipse. UI from
com.ibm.debug plugin interfaces to GDBPiclto control GDB which performs
the real debugging.
As for exploring and debugging GDBPicl, importing the source, building a
jar and putting it at the plugins directory is the first step. To
diagnose problems in GDBPicl and find out what is really happening, you
can make use the trace options in GDBPicl. GDBPicl supports two
categories of tracings, namely, event tracing and debug tracings. Trace
output will be generated by GdbPicl whenever there is a code fragment:
If (Gdb.traceLogger.DBG)
Gdb.traceLogger.dbg(2, "dbg message");
or
If (Gdb.traceLogger.EVT)
Gdb.traceLogger.evt(2, "evt message");
This code will generate messages if dbg and evt trace level is set to 2 or
higher.
Tracings can be invoked by specifying the following options when the picl
is started:
-DJT_EVT=# - where # could be 1,2, or 3
-DJT_DBT=# - where # could be 1,2, or 3
GdbPicl generates varying amounts of trace information depending on the
trace level you specify in these options. There are three levels of
tracings. "1" produces least amount of tracing information while a "3"
produces the most amount of information.
To enable tracing, extract DebugMiner.properties from
../plugins/org.eclipse.cdt.cpp.miners/miner/cpp_minerssrc.zi p.
Inside DebugMiner.properties, debug_options is defined as empty by default.
If yout append the aforementioned options to debug_options, GDBPicl will
produce tracing information when started. Tracing information will be
printed out in "Output" view. In case tracing info gets too big, simply
put the following in DebugMiner.properties:
debug_options=-DJT_EVT=1 -DJT_DBG=1 > output.txt 2>err.txt
and all output will be piped to output.txt and error will be sent to
err.txt in your current working directory.
After changing and saving DebugMiner.properties, simply restart Eclipse
and the changes should take effect. (You don't need to put this
properties file back to the zip.)
Thanks,
Samantha
johnrose@austin.ibm.com wrote:
> Hi -
> I am familiar with Eclipse but new to CDT, and I have been trying to
> dive into the code. I have two questions regarding CDT that any of the
> CDT developers could probably answer pretty quickly.
> First, I am having problems rebuilding the com.ibm.debug plugin with the
> source zips from CDT build 20020408. I am using the latest stable
> Eclipse build, from 20020321. I imported all of the CDT plugins (and
> their dependencies) to a workspace, and added the necessary plugins to
> the Projects tab under the Build Path property. When I try to rebuild
> com.ibm.debug I get errors about missing PICLDebugPlugin. Although
> there appears to be a PICLDebugPlugin.class in the included ibmdebug.jar
> file, there is no Java file to compile a new one. My only other idea is
> that the plugin.xml mentions PICLDebugPlugin as the class associated
> with the com.ibm.debug plugin. Any suggestions on how to rebuild this
> plugin would be appreciated.
> Secondly, I was curious about the best way to go about
> exploring/debugging the GdbPicl from within an Eclipse workspace. It
> seems to not technically be a plugin, as it has no plugin.xml. The only
> thing I have come up with so far is to import the src zips for the Picl,
> and replace the jar file manually in the eclipse/plugins directory after
> recompiling. Is there an easier way? Any suggestions on this would be
> a great help!
> Thanks everybody-
> John
|
|
|
| Re: Newbie Questions [message #24774 is a reply to message #24491] |
Thu, 18 April 2002 14:44 |
| Eclipse User |
|
|
|
I work on the debug plugin and will try to help.
First, we moved some classes from "internal" packages to "com.ibm.debug" and
our build didn't know about the change so the class was built but the source
wasn't picked up.
We are in the process of making more radical changes to the structure of the
com.ibm.debug plugin and after that will be looking at doing a better job of
allowing users like yourself build it.
<johnrose@austin.ibm.com> wrote in message
news:3CBCB6EA.AEF72BAA@austin.ibm.com...
> Hi -
>
> I am familiar with Eclipse but new to CDT, and I have been trying to
> dive into the code. I have two questions regarding CDT that any of the
> CDT developers could probably answer pretty quickly.
>
> First, I am having problems rebuilding the com.ibm.debug plugin with the
> source zips from CDT build 20020408. I am using the latest stable
> Eclipse build, from 20020321. I imported all of the CDT plugins (and
> their dependencies) to a workspace, and added the necessary plugins to
> the Projects tab under the Build Path property. When I try to rebuild
> com.ibm.debug I get errors about missing PICLDebugPlugin. Although
> there appears to be a PICLDebugPlugin.class in the included ibmdebug.jar
> file, there is no Java file to compile a new one. My only other idea is
> that the plugin.xml mentions PICLDebugPlugin as the class associated
> with the com.ibm.debug plugin. Any suggestions on how to rebuild this
> plugin would be appreciated.
>
> Secondly, I was curious about the best way to go about
> exploring/debugging the GdbPicl from within an Eclipse workspace. It
> seems to not technically be a plugin, as it has no plugin.xml. The only
> thing I have come up with so far is to import the src zips for the Picl,
> and replace the jar file manually in the eclipse/plugins directory after
> recompiling. Is there an easier way? Any suggestions on this would be
> a great help!
>
> Thanks everybody-
> John
>
|
|
|
| Re: Newbie Questions [message #24810 is a reply to message #24774] |
Thu, 18 April 2002 15:04 |
| Eclipse User |
|
|
|
Hi -
Thank you all for your responses. I will look forward to all of the
source being
included with the CDT downloads. In the interim, is the code for the
PICLDebugPlugin available anywhere for perusal? Old CVS dirs, etc? I
am
investigating the possibility of a PICL implementation for an alternate
debugger
(DBX on AIX), and this would be useful reading.
Your help is appreciated-
John
Alan Boxall wrote:
>
> I work on the debug plugin and will try to help.
>
> First, we moved some classes from "internal" packages to "com.ibm.debug" and
> our build didn't know about the change so the class was built but the source
> wasn't picked up.
>
> We are in the process of making more radical changes to the structure of the
> com.ibm.debug plugin and after that will be looking at doing a better job of
> allowing users like yourself build it.
>
> <johnrose@austin.ibm.com> wrote in message
> news:3CBCB6EA.AEF72BAA@austin.ibm.com...
> > Hi -
> >
> > I am familiar with Eclipse but new to CDT, and I have been trying to
> > dive into the code. I have two questions regarding CDT that any of the
> > CDT developers could probably answer pretty quickly.
> >
> > First, I am having problems rebuilding the com.ibm.debug plugin with the
> > source zips from CDT build 20020408. I am using the latest stable
> > Eclipse build, from 20020321. I imported all of the CDT plugins (and
> > their dependencies) to a workspace, and added the necessary plugins to
> > the Projects tab under the Build Path property. When I try to rebuild
> > com.ibm.debug I get errors about missing PICLDebugPlugin. Although
> > there appears to be a PICLDebugPlugin.class in the included ibmdebug.jar
> > file, there is no Java file to compile a new one. My only other idea is
> > that the plugin.xml mentions PICLDebugPlugin as the class associated
> > with the com.ibm.debug plugin. Any suggestions on how to rebuild this
> > plugin would be appreciated.
> >
> > Secondly, I was curious about the best way to go about
> > exploring/debugging the GdbPicl from within an Eclipse workspace. It
> > seems to not technically be a plugin, as it has no plugin.xml. The only
> > thing I have come up with so far is to import the src zips for the Picl,
> > and replace the jar file manually in the eclipse/plugins directory after
> > recompiling. Is there an easier way? Any suggestions on this would be
> > a great help!
> >
> > Thanks everybody-
> > John
> >
|
|
| |
| Re: Newbie Questions [message #24931 is a reply to message #24810] |
Fri, 19 April 2002 09:32 |
| Eclipse User |
|
|
|
The R1 version of the class(es) you need won't match the R2 code.
I will arrange to give the cdt team a new .jar and matching src.zip
I am working with Jeff to determine how we fix this in the future.
"John Rose" <a@a.com> wrote in message
news:3CBF18D4.C50193DD@austin.ibm.com...
>
> Hi -
>
> Thank you all for your responses. I will look forward to all of the
> source being
> included with the CDT downloads. In the interim, is the code for the
> PICLDebugPlugin available anywhere for perusal? Old CVS dirs, etc? I
> am
> investigating the possibility of a PICL implementation for an alternate
> debugger
> (DBX on AIX), and this would be useful reading.
>
> Your help is appreciated-
> John
>
>
> Alan Boxall wrote:
> >
> > I work on the debug plugin and will try to help.
> >
> > First, we moved some classes from "internal" packages to "com.ibm.debug"
and
> > our build didn't know about the change so the class was built but the
source
> > wasn't picked up.
> >
> > We are in the process of making more radical changes to the structure of
the
> > com.ibm.debug plugin and after that will be looking at doing a better
job of
> > allowing users like yourself build it.
> >
> > <johnrose@austin.ibm.com> wrote in message
> > news:3CBCB6EA.AEF72BAA@austin.ibm.com...
> > > Hi -
> > >
> > > I am familiar with Eclipse but new to CDT, and I have been trying to
> > > dive into the code. I have two questions regarding CDT that any of
the
> > > CDT developers could probably answer pretty quickly.
> > >
> > > First, I am having problems rebuilding the com.ibm.debug plugin with
the
> > > source zips from CDT build 20020408. I am using the latest stable
> > > Eclipse build, from 20020321. I imported all of the CDT plugins (and
> > > their dependencies) to a workspace, and added the necessary plugins to
> > > the Projects tab under the Build Path property. When I try to rebuild
> > > com.ibm.debug I get errors about missing PICLDebugPlugin. Although
> > > there appears to be a PICLDebugPlugin.class in the included
ibmdebug.jar
> > > file, there is no Java file to compile a new one. My only other idea
is
> > > that the plugin.xml mentions PICLDebugPlugin as the class associated
> > > with the com.ibm.debug plugin. Any suggestions on how to rebuild this
> > > plugin would be appreciated.
> > >
> > > Secondly, I was curious about the best way to go about
> > > exploring/debugging the GdbPicl from within an Eclipse workspace. It
> > > seems to not technically be a plugin, as it has no plugin.xml. The
only
> > > thing I have come up with so far is to import the src zips for the
Picl,
> > > and replace the jar file manually in the eclipse/plugins directory
after
> > > recompiling. Is there an easier way? Any suggestions on this would
be
> > > a great help!
> > >
> > > Thanks everybody-
> > > John
> > >
|
|
|
Goto Forum:
Current Time: Sat May 10 01:20:43 EDT 2025
Powered by FUDForum. Page generated in 0.03592 seconds |
Home