Debugging mode: Felix (through Pax) + Eclipse
|
View:
New views
7 Messages
—
Rating Filter:
Alert me
|
 |
Debugging mode: Felix (through Pax) + Eclipse
by Vlatko Davidovski-2
::
Rate this Message:
Hi!
A quick question, when I am using Felix through Pax Runner in Eclipse, seems debugging does not work. All breakpoints are ignored. Any trick to get the debugging working? Thanks! Vlatko --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: Debugging mode: Felix (through Pax) + Eclipse
by Toni Menzel-2
::
Rate this Message:
Yes: Remote debugging because paxrunner spawns Felix in a new process.
On 05.11.2009, at 13:52, Vlatko Davidovski <vdavidovski@...> wrote: > Hi! > > A quick question, when I am using Felix through Pax Runner in > Eclipse, seems debugging does not work. All breakpoints are ignored. > Any trick to get the debugging working? > > Thanks! > Vlatko > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@... > For additional commands, e-mail: users-help@... > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: Debugging mode: Felix (through Pax) + Eclipse
by Vlatko Davidovski-2
::
Rate this Message:
Thanks for your reply Toni!
Can you be more specific how to do this? On Nov 5, 2009, at 2:29 PM, Toni Menzel wrote: > Yes: Remote debugging because paxrunner spawns Felix in a new process. > > On 05.11.2009, at 13:52, Vlatko Davidovski <vdavidovski@...> > wrote: > >> Hi! >> >> A quick question, when I am using Felix through Pax Runner in >> Eclipse, seems debugging does not work. All breakpoints are ignored. >> Any trick to get the debugging working? >> >> Thanks! >> Vlatko >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscribe@... >> For additional commands, e-mail: users-help@... >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@... > For additional commands, e-mail: users-help@... > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: Debugging mode: Felix (through Pax) + Eclipse
by Stuart McCulloch
::
Rate this Message:
2009/11/5 Toni Menzel <tonimenzel@...>
> Yes: Remote debugging because paxrunner spawns Felix in a new process. well even standard Eclipse JDT launches a new process when debugging, so it's more about whether Eclipse can communicate properly with the target VM I thought this was working a year or so ago - at least I remember I made a few changes to allow Eclipse to control the launching of the new runner process so it can add the various debugging switches, etc. (ie. the whole JavaRunner API) but it's also been a while since I used pax-eclipse, so maybe something broke in the last year or so... whoever looks into this needs to compare the JVM args passed to the debugged process* when using raw JDT compared to pax-eclipse (* you can use jvisualvm to attach to the debugged process and get a dump) sorry I can't be more specific On 05.11.2009, at 13:52, Vlatko Davidovski <vdavidovski@...> wrote: > > Hi! >> >> A quick question, when I am using Felix through Pax Runner in Eclipse, >> seems debugging does not work. All breakpoints are ignored. >> Any trick to get the debugging working? >> >> Thanks! >> Vlatko >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscribe@... >> For additional commands, e-mail: users-help@... >> >> > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@... > For additional commands, e-mail: users-help@... > > -- Cheers, Stuart |
|
|
Re: Debugging mode: Felix (through Pax) + Eclipse
by Vlatko Davidovski-2
::
Rate this Message:
Thanks Stuart! I do the following: 1. RUN pax runner from Eclipse with the following option: --vmOptions="-Xdebug - Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005" 2. DEBUG using Remote Java Application with options: localhost and 5005 One can see it connects, because I have the option suspend=y, so pax runner continues starting the OSGi framework only after starting the debugger on remote java application. However, nothing happens on the places where I have breakpoints attached. Any ideas how to resolve this? Thanks! Vlatko On Nov 5, 2009, at 4:05 PM, Stuart McCulloch wrote: > 2009/11/5 Toni Menzel <tonimenzel@...> > >> Yes: Remote debugging because paxrunner spawns Felix in a new >> process. > > > well even standard Eclipse JDT launches a new process when > debugging, so > it's more about whether Eclipse can communicate properly with the > target VM > > I thought this was working a year or so ago - at least I remember I > made a > few > changes to allow Eclipse to control the launching of the new runner > process > so > it can add the various debugging switches, etc. (ie. the whole > JavaRunner > API) > > but it's also been a while since I used pax-eclipse, so maybe > something > broke > in the last year or so... whoever looks into this needs to compare > the JVM > args > passed to the debugged process* when using raw JDT compared to pax- > eclipse > > (* you can use jvisualvm to attach to the debugged process and get a > dump) > > sorry I can't be more specific > > On 05.11.2009, at 13:52, Vlatko Davidovski <vdavidovski@...> > wrote: >> >> Hi! >>> >>> A quick question, when I am using Felix through Pax Runner in >>> Eclipse, >>> seems debugging does not work. All breakpoints are ignored. >>> Any trick to get the debugging working? >>> >>> Thanks! >>> Vlatko >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscribe@... >>> For additional commands, e-mail: users-help@... >>> >>> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscribe@... >> For additional commands, e-mail: users-help@... >> >> > > > -- > Cheers, Stuart |
|
|
Re: Debugging mode: Felix (through Pax) + Eclipse
by Stuart McCulloch
::
Rate this Message:
2009/11/5 Vlatko Davidovski <vdavidovski@...>
> > Thanks Stuart! > > I do the following: > 1. RUN pax runner from Eclipse with the following option: > --vmOptions="-Xdebug > -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005" > 2. DEBUG using Remote Java Application with options: localhost and 5005 > > One can see it connects, because I have the option suspend=y, so pax runner > continues starting the OSGi framework only after starting the debugger on > remote java application. > However, nothing happens on the places where I have breakpoints attached. > > Any ideas how to resolve this? > BTW, are you using the Pax Runner Plugin for Eclipse... http://paxrunner.ops4j.org/display/paxrunner/Eclipse+Plugin or are you launching Pax Runner as a plain Java application? breakpoint debugging will only work using the Pax Runner Plugin for Eclipse, because it has the necessary integration with Eclipse to launch the process if you try to debug Pax Runner as a plain Java application then you'll just end up debugging the standalone launcher rather than the launched application. > Thanks! > Vlatko > > On Nov 5, 2009, at 4:05 PM, Stuart McCulloch wrote: > > 2009/11/5 Toni Menzel <tonimenzel@...> >> >> Yes: Remote debugging because paxrunner spawns Felix in a new process. >>> >> >> >> well even standard Eclipse JDT launches a new process when debugging, so >> it's more about whether Eclipse can communicate properly with the target >> VM >> >> I thought this was working a year or so ago - at least I remember I made a >> few >> changes to allow Eclipse to control the launching of the new runner >> process >> so >> it can add the various debugging switches, etc. (ie. the whole JavaRunner >> API) >> >> but it's also been a while since I used pax-eclipse, so maybe something >> broke >> in the last year or so... whoever looks into this needs to compare the JVM >> args >> passed to the debugged process* when using raw JDT compared to pax-eclipse >> >> (* you can use jvisualvm to attach to the debugged process and get a dump) >> >> sorry I can't be more specific >> >> On 05.11.2009, at 13:52, Vlatko Davidovski <vdavidovski@...> wrote: >> >>> >>> Hi! >>> >>>> >>>> A quick question, when I am using Felix through Pax Runner in Eclipse, >>>> seems debugging does not work. All breakpoints are ignored. >>>> Any trick to get the debugging working? >>>> >>>> Thanks! >>>> Vlatko >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: users-unsubscribe@... >>>> For additional commands, e-mail: users-help@... >>>> >>>> >>>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscribe@... >>> For additional commands, e-mail: users-help@... >>> >>> >>> >> >> -- >> Cheers, Stuart >> > > -- Cheers, Stuart |
|
|
Re: Debugging mode: Felix (through Pax) + Eclipse
by Vlatko Davidovski-2
::
Rate this Message:
On Nov 5, 2009, at 5:07 PM, Stuart McCulloch wrote: > 2009/11/5 Vlatko Davidovski <vdavidovski@...> > >> >> Thanks Stuart! >> >> I do the following: >> 1. RUN pax runner from Eclipse with the following option: >> --vmOptions="-Xdebug >> -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005" >> 2. DEBUG using Remote Java Application with options: localhost and >> 5005 >> >> One can see it connects, because I have the option suspend=y, so >> pax runner >> continues starting the OSGi framework only after starting the >> debugger on >> remote java application. >> However, nothing happens on the places where I have breakpoints >> attached. >> >> Any ideas how to resolve this? >> > > BTW, are you using the Pax Runner Plugin for Eclipse... > > http://paxrunner.ops4j.org/display/paxrunner/Eclipse+Plugin breakpoints... No clue why. > > or are you launching Pax Runner as a plain Java application? > > breakpoint debugging will only work using the Pax Runner Plugin for > Eclipse, > because it has the necessary integration with Eclipse to launch the > process > > if you try to debug Pax Runner as a plain Java application then > you'll just > end > up debugging the standalone launcher rather than the launched > application. > > >> Thanks! >> Vlatko >> >> On Nov 5, 2009, at 4:05 PM, Stuart McCulloch wrote: >> >> 2009/11/5 Toni Menzel <tonimenzel@...> >>> >>> Yes: Remote debugging because paxrunner spawns Felix in a new >>> process. >>>> >>> >>> >>> well even standard Eclipse JDT launches a new process when >>> debugging, so >>> it's more about whether Eclipse can communicate properly with the >>> target >>> VM >>> >>> I thought this was working a year or so ago - at least I remember >>> I made a >>> few >>> changes to allow Eclipse to control the launching of the new runner >>> process >>> so >>> it can add the various debugging switches, etc. (ie. the whole >>> JavaRunner >>> API) >>> >>> but it's also been a while since I used pax-eclipse, so maybe >>> something >>> broke >>> in the last year or so... whoever looks into this needs to compare >>> the JVM >>> args >>> passed to the debugged process* when using raw JDT compared to pax- >>> eclipse >>> >>> (* you can use jvisualvm to attach to the debugged process and get >>> a dump) >>> >>> sorry I can't be more specific >>> >>> On 05.11.2009, at 13:52, Vlatko Davidovski <vdavidovski@...> >>> wrote: >>> >>>> >>>> Hi! >>>> >>>>> >>>>> A quick question, when I am using Felix through Pax Runner in >>>>> Eclipse, >>>>> seems debugging does not work. All breakpoints are ignored. >>>>> Any trick to get the debugging working? >>>>> >>>>> Thanks! >>>>> Vlatko >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: users-unsubscribe@... >>>>> For additional commands, e-mail: users-help@... >>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: users-unsubscribe@... >>>> For additional commands, e-mail: users-help@... >>>> >>>> >>>> >>> >>> -- >>> Cheers, Stuart >>> >> >> > > > -- > Cheers, Stuart --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
| Free embeddable forum powered by Nabble | Forum Help |
