| stdout and stderr problem [message #169060] |
Fri, 16 July 2004 17:42  |
Eclipse User |
|
|
|
Originally posted by: dtwchiu.hotmail.com
Hi,
I am writing an action that will launch a Java application using the
IVMRunner interface and for some reason, the application does not come up
at all. I stepped through the StandardVMRunner class and it seems all the
arguments and environment variables are set properly. I can also see the
process running using "ps" command, but the UI does not come up nor does
anything get logged into the application log. To help me debug this
problem, I would like to know that if the stdout and the stderr of the
application are automatically pipe out to the console window. If not, how
can I do that. Right now, I am not seeing any output except seeing the
process is running.
Thanks.
David.
|
|
|
|
|
| Re: stdout and stderr problem [message #169557 is a reply to message #169084] |
Tue, 20 July 2004 14:11  |
| Eclipse User |
|
|
|
Originally posted by: turker.keskinpala.vanderbilt.edu
Hi,
When I read your reply, I was working on something similar. I was having the
same problem when I used the VMRunner approach. Thanks for the tip. This
helped me to run my app in debug mode.
I would like to ask a follow-up question. I would like to be able to
programmatically step through the code that I am debugging or get some info
during the debug. For this, I should be able to get the debug events, I
suppose. I know that one has to implement an IDebugEventSetListener to be
able to receive events during debug. However, I cannot figure out how to go
about doing this. When you use IVMRunner.run, it contributes results to
debug targets and processes to the given launch. What happens when using
DebugToolsUI.launch? Well, apparently, I am confused about this.
I will appreciate if you could provide some help with this.
Thanks for your time,
Turker Keskinpala
"Rich Kulp" <richkulp@NO.SPAM.us.ibm.com> wrote in message
news:cd9mre$25g$1@eclipse.org...
> If you are just launching a vm with nothing fancy but using the
> classpath of a project, then you can just use the standard java launch
> configuration on your own and setup the parameters and such.
>
> See:
>
> http://www.eclipse.org/articles/Article-Java-launch/launchin g-java.html
>
> for how to just launch a vm against a project.
>
> Otherwise you should write your launcher instead. Those when launched
> properly will add themselves to the console log. The IVMRunner is now a
> class used within launchers. It is not typically used by itself.
>
> See:
>
> http://www.eclipse.org/articles/Article-Launch-Framework/lau nch.html
>
> for how to create your own launcher.
>
>
> --
> Thanks, Rich Kulp
>
>
|
|
|
| Re: stdout and stderr problem [message #169565 is a reply to message #169557] |
Tue, 20 July 2004 14:22 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.NO.SPAM.us.ibm.com
Sorry, can't help with that. I never did that. Maybe somebody else can
answer that question.
> I would like to ask a follow-up question. I would like to be able to
> programmatically step through the code that I am debugging or get some info
> during the debug. For this, I should be able to get the debug events, I
> suppose. I know that one has to implement an IDebugEventSetListener to be
> able to receive events during debug. However, I cannot figure out how to go
> about doing this. When you use IVMRunner.run, it contributes results to
> debug targets and processes to the given launch. What happens when using
> DebugToolsUI.launch? Well, apparently, I am confused about this.
>
> I will appreciate if you could provide some help with this.
>
> Thanks for your time,
> Turker Keskinpala
--
Thanks, Rich Kulp
|
|
|
| Re: stdout and stderr problem [message #169657 is a reply to message #169557] |
Wed, 21 July 2004 09:45 |
| Eclipse User |
|
|
|
Just register your IDebugEventSetListener with the DebugPlugin. You will
receive all debug events from all registered targets.
Darin
"Turker Keskinpala" <turker.keskinpala@vanderbilt.edu> wrote in message
news:cdjn4v$8nq$1@eclipse.org...
> Hi,
>
> When I read your reply, I was working on something similar. I was having
the
> same problem when I used the VMRunner approach. Thanks for the tip. This
> helped me to run my app in debug mode.
>
> I would like to ask a follow-up question. I would like to be able to
> programmatically step through the code that I am debugging or get some
info
> during the debug. For this, I should be able to get the debug events, I
> suppose. I know that one has to implement an IDebugEventSetListener to be
> able to receive events during debug. However, I cannot figure out how to
go
> about doing this. When you use IVMRunner.run, it contributes results to
> debug targets and processes to the given launch. What happens when using
> DebugToolsUI.launch? Well, apparently, I am confused about this.
>
> I will appreciate if you could provide some help with this.
>
> Thanks for your time,
> Turker Keskinpala
>
>
> "Rich Kulp" <richkulp@NO.SPAM.us.ibm.com> wrote in message
> news:cd9mre$25g$1@eclipse.org...
> > If you are just launching a vm with nothing fancy but using the
> > classpath of a project, then you can just use the standard java launch
> > configuration on your own and setup the parameters and such.
> >
> > See:
> >
> > http://www.eclipse.org/articles/Article-Java-launch/launchin g-java.html
> >
> > for how to just launch a vm against a project.
> >
> > Otherwise you should write your launcher instead. Those when launched
> > properly will add themselves to the console log. The IVMRunner is now a
> > class used within launchers. It is not typically used by itself.
> >
> > See:
> >
> > http://www.eclipse.org/articles/Article-Launch-Framework/lau nch.html
> >
> > for how to create your own launcher.
> >
> >
> > --
> > Thanks, Rich Kulp
> >
> >
>
>
|
|
|
| Re: stdout and stderr problem [message #169688 is a reply to message #169657] |
Wed, 21 July 2004 12:19 |
| Eclipse User |
|
|
|
Originally posted by: turker.keskinpala.vanderbilt.edu
Thanks for your reply. I'll assume the debug target will automatically be
registered when DebugUITools.launch(configuration,ILaunchManager.DEBUG_MODE)
executes. I'll see soon if this is true:-)
Turker
"Darin Wright" <Darin_Wright@ca.ibm.com> wrote in message
news:cdls6p$hl6$1@eclipse.org...
> Just register your IDebugEventSetListener with the DebugPlugin. You will
> receive all debug events from all registered targets.
>
> Darin
>
> "Turker Keskinpala" <turker.keskinpala@vanderbilt.edu> wrote in message
> news:cdjn4v$8nq$1@eclipse.org...
> > Hi,
> >
> > When I read your reply, I was working on something similar. I was having
> the
> > same problem when I used the VMRunner approach. Thanks for the tip. This
> > helped me to run my app in debug mode.
> >
> > I would like to ask a follow-up question. I would like to be able to
> > programmatically step through the code that I am debugging or get some
> info
> > during the debug. For this, I should be able to get the debug events, I
> > suppose. I know that one has to implement an IDebugEventSetListener to
be
> > able to receive events during debug. However, I cannot figure out how to
> go
> > about doing this. When you use IVMRunner.run, it contributes results to
> > debug targets and processes to the given launch. What happens when using
> > DebugToolsUI.launch? Well, apparently, I am confused about this.
> >
> > I will appreciate if you could provide some help with this.
> >
> > Thanks for your time,
> > Turker Keskinpala
> >
> >
> > "Rich Kulp" <richkulp@NO.SPAM.us.ibm.com> wrote in message
> > news:cd9mre$25g$1@eclipse.org...
> > > If you are just launching a vm with nothing fancy but using the
> > > classpath of a project, then you can just use the standard java launch
> > > configuration on your own and setup the parameters and such.
> > >
> > > See:
> > >
> > >
http://www.eclipse.org/articles/Article-Java-launch/launchin g-java.html
> > >
> > > for how to just launch a vm against a project.
> > >
> > > Otherwise you should write your launcher instead. Those when launched
> > > properly will add themselves to the console log. The IVMRunner is now
a
> > > class used within launchers. It is not typically used by itself.
> > >
> > > See:
> > >
> > > http://www.eclipse.org/articles/Article-Launch-Framework/lau nch.html
> > >
> > > for how to create your own launcher.
> > >
> > >
> > > --
> > > Thanks, Rich Kulp
> > >
> > >
> >
> >
>
>
|
|
|
|
|
| Re: stdout and stderr problem [message #170114 is a reply to message #170098] |
Mon, 26 July 2004 17:49 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.NO.SPAM.us.ibm.com
How are you adding them to your classpath? Are you making them system
type classpath entries in java build path? If so, then just make sure
they are after the JRE_CONTAINER or JRE_LIB entries in the classpath.
--
Thanks, Rich Kulp
|
|
|
Powered by
FUDForum. Page generated in 0.29040 seconds
Home