Debugging problems in 6.2.1a

bridged with qdn.public.devtools
Rüdiger Loos

Debugging problems in 6.2.1a

Post by Rüdiger Loos » Wed Aug 06, 2003 12:30 pm

Hallo,

I have a big problem in debugging my QNX application.
I build my apps without any error and warning.
But when I start to debug my apps, I get a "Launch Configuration Error" with
one of the following informations:
"Exception occured processing launch configuration. Reason: Failed Launching
CDI Debugger: Error initializing: Exec error:Launching failed" or
"Exception occured : Not enough memory"

Can anybody help me.

Thanks a lot
Rüdiger

David Gibbs

Re: Debugging problems in 6.2.1a

Post by David Gibbs » Wed Aug 06, 2003 4:51 pm

"Ruediger Loos" <Ruediger.Loos@3soft.de> wrote:
Hallo,

I have a big problem in debugging my QNX application.
I build my apps without any error and warning.
But when I start to debug my apps, I get a "Launch Configuration Error" with
one of the following informations:
"Exception occured processing launch configuration. Reason: Failed Launching
CDI Debugger: Error initializing: Exec error:Launching failed" or
"Exception occured : Not enough memory"

Can anybody help me.
There's probably a .log file generated in workspace/.metadata, can you
post the corresponding entry?

Also, what host are you running on?

Are you out of/low on system memory?

What type of project is it? (QNX C/C++? Standard Make?)

-David
--
QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.

Rüdiger Loos

Re: Debugging problems in 6.2.1a

Post by Rüdiger Loos » Thu Aug 07, 2003 9:23 am

Hallo David,

I think the important entries are:

--------------------------
!ENTRY org.eclipse.debug.ui 4 120 Jun 17, 2003 12:47:13.220
!MESSAGE Error logged from Debug UI:
!STACK 1
org.eclipse.core.runtime.CoreException[503]: java.io.IOException: Open Not
enough memory
at
com.qnx.tools.utils.target.TargetServiceFile.connect(TargetServiceFile.java:
347)
at
com.qnx.tools.utils.target.TargetServiceFile.creat(TargetServiceFile.java:24
3)
at
com.qnx.tools.utils.target.TargetFileDownload.download(TargetFileDownload.ja
va:54)
at
com.qnx.tools.ide.qde.internal.ui.launch.LaunchConfigurationDelegate.perform
FileTransfer(LaunchConfigurationDelegate.java:443)
at
com.qnx.tools.ide.qde.internal.ui.launch.LaunchConfigurationDelegate.launch(
LaunchConfigurationDelegate.java:144)
at
org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigurati
on.java:136)
at
org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationDialog
$10.run(LaunchConfigurationDialog.java:2299)
at
org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext
..java:98)
!ENTRY com.qnx.tools.ide.qde.ui 4 503 Jun 17, 2003 12:47:13.220
!MESSAGE Can't transfer file for etx : Open Not enough memory
!STACK 0
java.io.IOException: Open Not enough memory
at
com.qnx.tools.utils.target.TargetServiceFile.connect(TargetServiceFile.java:
347)
at
com.qnx.tools.utils.target.TargetServiceFile.creat(TargetServiceFile.java:24
3)
at
com.qnx.tools.utils.target.TargetFileDownload.download(TargetFileDownload.ja
va:54)
at
com.qnx.tools.ide.qde.internal.ui.launch.LaunchConfigurationDelegate.perform
FileTransfer(LaunchConfigurationDelegate.java:443)
at
com.qnx.tools.ide.qde.internal.ui.launch.LaunchConfigurationDelegate.launch(
LaunchConfigurationDelegate.java:144)
at
org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigurati
on.java:136)
at
org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationDialog
$10.run(LaunchConfigurationDialog.java:2299)
at
org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext
..java:98)
-------

and

-------
!ENTRY org.eclipse.debug.ui 4 120 Apr 07, 2003 15:13:49.875
!MESSAGE Error logged from Debug UI:
!STACK 1
org.eclipse.core.runtime.CoreException[150]: java.io.IOException: Exec
error:Launching failed
at org.eclipse.cdt.utils.spawner.Spawner.exec(Spawner.java:215)
at org.eclipse.cdt.utils.spawner.Spawner.<init>(Spawner.java:48)
at
org.eclipse.cdt.utils.spawner.ProcessFactory.exec(ProcessFactory.java:70)
at
org.eclipse.cdt.launch.internal.LocalCLaunchConfigurationDelegate.exec(Local
CLaunchConfigurationDelegate.java:213)
at
org.eclipse.cdt.launch.internal.LocalCLaunchConfigurationDelegate.launch(Loc
alCLaunchConfigurationDelegate.java:138)
at
org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigurati
on.java:136)
at
org.eclipse.debug.internal.ui.actions.RelaunchActionDelegate.relaunch(Relaun
chActionDelegate.java:56)
at
org.eclipse.debug.internal.ui.actions.RelaunchActionDelegate.relaunch(Relaun
chActionDelegate.java:32)
at
org.eclipse.debug.internal.ui.actions.RelaunchHistoryLaunchAction$1.run(Rela
unchHistoryLaunchAction.java:59)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:66)
at
org.eclipse.debug.internal.ui.actions.RelaunchHistoryLaunchAction.run(Relaun
chHistoryLaunchAction.java:57)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:749)
at
org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(Action
ContributionItem.java:407)
at
org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent(ActionCont
ributionItem.java:361)
at
org.eclipse.jface.action.ActionContributionItem.access$0(ActionContributionI
tem.java:352)
at
org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent(A
ctionContributionItem.java:47)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:77)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:827)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:1529)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1291)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1343)
at org.eclipse.ui.internal.Workbench.run(Workbench.java:1326)
at
org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.jav
a:831)
at org.eclipse.core.boot.BootLoader.run(BootLoader.java:462)
at java.lang.reflect.Method.invoke(Native Method)
at org.eclipse.core.launcher.Main.basicRun(Main.java:247)
at org.eclipse.core.launcher.Main.run(Main.java:703)
at org.eclipse.core.launcher.Main.main(Main.java:539)
-----

My momentics is running on a Windows XP PC an connected via Ethernet with my
X86 target.

The type of project is a "QNX C Application Project".

Regards

Rüdiger

P.S. I've heard of a patchB for Momentics 6.2.1 that should solve the
problem?!?


"David Gibbs" <dagibbs@qnx.com> schrieb im Newsbeitrag
news:bgrblu$j0n$2@nntp.qnx.com...
"Ruediger Loos" <Ruediger.Loos@3soft.de> wrote:
Hallo,

I have a big problem in debugging my QNX application.
I build my apps without any error and warning.
But when I start to debug my apps, I get a "Launch Configuration Error"
with
one of the following informations:
"Exception occured processing launch configuration. Reason: Failed
Launching
CDI Debugger: Error initializing: Exec error:Launching failed" or
"Exception occured : Not enough memory"

Can anybody help me.

There's probably a .log file generated in workspace/.metadata, can you
post the corresponding entry?

Also, what host are you running on?

Are you out of/low on system memory?

What type of project is it? (QNX C/C++? Standard Make?)

-David
--
QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.

Mikhail Khodjaiants

Re: Debugging problems in 6.2.1a

Post by Mikhail Khodjaiants » Thu Aug 07, 2003 3:09 pm

It seems that your target is running out of memory.

Mikhail

"Rüdiger Loos" <Ruediger.Loos@3SOFT.de> wrote in message
news:bgt56j$3o5$1@inn.qnx.com...
Hallo David,

I think the important entries are:

--------------------------
!ENTRY org.eclipse.debug.ui 4 120 Jun 17, 2003 12:47:13.220
!MESSAGE Error logged from Debug UI:
!STACK 1
org.eclipse.core.runtime.CoreException[503]: java.io.IOException: Open Not
enough memory
at

com.qnx.tools.utils.target.TargetServiceFile.connect(TargetServiceFile.java:
347)
at

com.qnx.tools.utils.target.TargetServiceFile.creat(TargetServiceFile.java:24
3)
at

com.qnx.tools.utils.target.TargetFileDownload.download(TargetFileDownload.ja
va:54)
at

com.qnx.tools.ide.qde.internal.ui.launch.LaunchConfigurationDelegate.perform
FileTransfer(LaunchConfigurationDelegate.java:443)
at

com.qnx.tools.ide.qde.internal.ui.launch.LaunchConfigurationDelegate.launch(
LaunchConfigurationDelegate.java:144)
at

org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigurati
on.java:136)
at

org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationDialog
$10.run(LaunchConfigurationDialog.java:2299)
at

org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext
.java:98)
!ENTRY com.qnx.tools.ide.qde.ui 4 503 Jun 17, 2003 12:47:13.220
!MESSAGE Can't transfer file for etx : Open Not enough memory
!STACK 0
java.io.IOException: Open Not enough memory
at

com.qnx.tools.utils.target.TargetServiceFile.connect(TargetServiceFile.java:
347)
at

com.qnx.tools.utils.target.TargetServiceFile.creat(TargetServiceFile.java:24
3)
at

com.qnx.tools.utils.target.TargetFileDownload.download(TargetFileDownload.ja
va:54)
at

com.qnx.tools.ide.qde.internal.ui.launch.LaunchConfigurationDelegate.perform
FileTransfer(LaunchConfigurationDelegate.java:443)
at

com.qnx.tools.ide.qde.internal.ui.launch.LaunchConfigurationDelegate.launch(
LaunchConfigurationDelegate.java:144)
at

org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigurati
on.java:136)
at

org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationDialog
$10.run(LaunchConfigurationDialog.java:2299)
at

org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext
.java:98)
-------

and

-------
!ENTRY org.eclipse.debug.ui 4 120 Apr 07, 2003 15:13:49.875
!MESSAGE Error logged from Debug UI:
!STACK 1
org.eclipse.core.runtime.CoreException[150]: java.io.IOException: Exec
error:Launching failed
at org.eclipse.cdt.utils.spawner.Spawner.exec(Spawner.java:215)
at org.eclipse.cdt.utils.spawner.Spawner.<init>(Spawner.java:48)
at
org.eclipse.cdt.utils.spawner.ProcessFactory.exec(ProcessFactory.java:70)
at

org.eclipse.cdt.launch.internal.LocalCLaunchConfigurationDelegate.exec(Local
CLaunchConfigurationDelegate.java:213)
at

org.eclipse.cdt.launch.internal.LocalCLaunchConfigurationDelegate.launch(Loc
alCLaunchConfigurationDelegate.java:138)
at

org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigurati
on.java:136)
at

org.eclipse.debug.internal.ui.actions.RelaunchActionDelegate.relaunch(Relaun
chActionDelegate.java:56)
at

org.eclipse.debug.internal.ui.actions.RelaunchActionDelegate.relaunch(Relaun
chActionDelegate.java:32)
at

org.eclipse.debug.internal.ui.actions.RelaunchHistoryLaunchAction$1.run(Rela
unchHistoryLaunchAction.java:59)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:66)
at

org.eclipse.debug.internal.ui.actions.RelaunchHistoryLaunchAction.run(Relaun
chHistoryLaunchAction.java:57)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:749)
at

org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(Action
ContributionItem.java:407)
at

org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent(ActionCont
ributionItem.java:361)
at

org.eclipse.jface.action.ActionContributionItem.access$0(ActionContributionI
tem.java:352)
at

org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent(A
ctionContributionItem.java:47)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:77)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:827)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:1529)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1291)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1343)
at org.eclipse.ui.internal.Workbench.run(Workbench.java:1326)
at

org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.jav
a:831)
at org.eclipse.core.boot.BootLoader.run(BootLoader.java:462)
at java.lang.reflect.Method.invoke(Native Method)
at org.eclipse.core.launcher.Main.basicRun(Main.java:247)
at org.eclipse.core.launcher.Main.run(Main.java:703)
at org.eclipse.core.launcher.Main.main(Main.java:539)
-----

My momentics is running on a Windows XP PC an connected via Ethernet with
my
X86 target.

The type of project is a "QNX C Application Project".

Regards

Rüdiger

P.S. I've heard of a patchB for Momentics 6.2.1 that should solve the
problem?!?


"David Gibbs" <dagibbs@qnx.com> schrieb im Newsbeitrag
news:bgrblu$j0n$2@nntp.qnx.com...
"Ruediger Loos" <Ruediger.Loos@3soft.de> wrote:
Hallo,

I have a big problem in debugging my QNX application.
I build my apps without any error and warning.
But when I start to debug my apps, I get a "Launch Configuration
Error"
with
one of the following informations:
"Exception occured processing launch configuration. Reason: Failed
Launching
CDI Debugger: Error initializing: Exec error:Launching failed" or
"Exception occured : Not enough memory"

Can anybody help me.

There's probably a .log file generated in workspace/.metadata, can you
post the corresponding entry?

Also, what host are you running on?

Are you out of/low on system memory?

What type of project is it? (QNX C/C++? Standard Make?)

-David
--
QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.

Rüdiger Loos

Re: Debugging problems in 6.2.1a

Post by Rüdiger Loos » Fri Aug 08, 2003 9:00 am

No Mikhail, it does not.
This happens with every single application trying to debug.
I have 128MB RAM on my target and I can't debug a "hello world" program :-(

Rüdiger

"Mikhail Khodjaiants" <mikhailk@qnx.com> schrieb im Newsbeitrag
news:bgtqdo$je3$1@nntp.qnx.com...
It seems that your target is running out of memory.

Mikhail

"Rüdiger Loos" <Ruediger.Loos@3SOFT.de> wrote in message
news:bgt56j$3o5$1@inn.qnx.com...
Hallo David,

I think the important entries are:

--------------------------
!ENTRY org.eclipse.debug.ui 4 120 Jun 17, 2003 12:47:13.220
!MESSAGE Error logged from Debug UI:
!STACK 1
org.eclipse.core.runtime.CoreException[503]: java.io.IOException: Open
Not
enough memory
at


com.qnx.tools.utils.target.TargetServiceFile.connect(TargetServiceFile.java:
347)
at


com.qnx.tools.utils.target.TargetServiceFile.creat(TargetServiceFile.java:24
3)
at


com.qnx.tools.utils.target.TargetFileDownload.download(TargetFileDownload.ja
va:54)
at


com.qnx.tools.ide.qde.internal.ui.launch.LaunchConfigurationDelegate.perform
FileTransfer(LaunchConfigurationDelegate.java:443)
at


com.qnx.tools.ide.qde.internal.ui.launch.LaunchConfigurationDelegate.launch(
LaunchConfigurationDelegate.java:144)
at


org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigurati
on.java:136)
at


org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationDialog
$10.run(LaunchConfigurationDialog.java:2299)
at


org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext
.java:98)
!ENTRY com.qnx.tools.ide.qde.ui 4 503 Jun 17, 2003 12:47:13.220
!MESSAGE Can't transfer file for etx : Open Not enough memory
!STACK 0
java.io.IOException: Open Not enough memory
at


com.qnx.tools.utils.target.TargetServiceFile.connect(TargetServiceFile.java:
347)
at


com.qnx.tools.utils.target.TargetServiceFile.creat(TargetServiceFile.java:24
3)
at


com.qnx.tools.utils.target.TargetFileDownload.download(TargetFileDownload.ja
va:54)
at


com.qnx.tools.ide.qde.internal.ui.launch.LaunchConfigurationDelegate.perform
FileTransfer(LaunchConfigurationDelegate.java:443)
at


com.qnx.tools.ide.qde.internal.ui.launch.LaunchConfigurationDelegate.launch(
LaunchConfigurationDelegate.java:144)
at


org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigurati
on.java:136)
at


org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationDialog
$10.run(LaunchConfigurationDialog.java:2299)
at


org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext
.java:98)
-------

and

-------
!ENTRY org.eclipse.debug.ui 4 120 Apr 07, 2003 15:13:49.875
!MESSAGE Error logged from Debug UI:
!STACK 1
org.eclipse.core.runtime.CoreException[150]: java.io.IOException: Exec
error:Launching failed
at org.eclipse.cdt.utils.spawner.Spawner.exec(Spawner.java:215)
at org.eclipse.cdt.utils.spawner.Spawner.<init>(Spawner.java:48)
at

org.eclipse.cdt.utils.spawner.ProcessFactory.exec(ProcessFactory.java:70)
at


org.eclipse.cdt.launch.internal.LocalCLaunchConfigurationDelegate.exec(Local
CLaunchConfigurationDelegate.java:213)
at


org.eclipse.cdt.launch.internal.LocalCLaunchConfigurationDelegate.launch(Loc
alCLaunchConfigurationDelegate.java:138)
at


org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigurati
on.java:136)
at


org.eclipse.debug.internal.ui.actions.RelaunchActionDelegate.relaunch(Relaun
chActionDelegate.java:56)
at


org.eclipse.debug.internal.ui.actions.RelaunchActionDelegate.relaunch(Relaun
chActionDelegate.java:32)
at


org.eclipse.debug.internal.ui.actions.RelaunchHistoryLaunchAction$1.run(Rela
unchHistoryLaunchAction.java:59)
at
org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:66)
at


org.eclipse.debug.internal.ui.actions.RelaunchHistoryLaunchAction.run(Relaun
chHistoryLaunchAction.java:57)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:749)
at


org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(Action
ContributionItem.java:407)
at


org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent(ActionCont
ributionItem.java:361)
at


org.eclipse.jface.action.ActionContributionItem.access$0(ActionContributionI
tem.java:352)
at


org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent(A
ctionContributionItem.java:47)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:77)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:827)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:1529)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1291)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1343)
at org.eclipse.ui.internal.Workbench.run(Workbench.java:1326)
at


org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.jav
a:831)
at org.eclipse.core.boot.BootLoader.run(BootLoader.java:462)
at java.lang.reflect.Method.invoke(Native Method)
at org.eclipse.core.launcher.Main.basicRun(Main.java:247)
at org.eclipse.core.launcher.Main.run(Main.java:703)
at org.eclipse.core.launcher.Main.main(Main.java:539)
-----

My momentics is running on a Windows XP PC an connected via Ethernet
with
my
X86 target.

The type of project is a "QNX C Application Project".

Regards

Rüdiger

P.S. I've heard of a patchB for Momentics 6.2.1 that should solve the
problem?!?


"David Gibbs" <dagibbs@qnx.com> schrieb im Newsbeitrag
news:bgrblu$j0n$2@nntp.qnx.com...
"Ruediger Loos" <Ruediger.Loos@3soft.de> wrote:
Hallo,

I have a big problem in debugging my QNX application.
I build my apps without any error and warning.
But when I start to debug my apps, I get a "Launch Configuration
Error"
with
one of the following informations:
"Exception occured processing launch configuration. Reason: Failed
Launching
CDI Debugger: Error initializing: Exec error:Launching failed" or
"Exception occured : Not enough memory"

Can anybody help me.

There's probably a .log file generated in workspace/.metadata, can you
post the corresponding entry?

Also, what host are you running on?

Are you out of/low on system memory?

What type of project is it? (QNX C/C++? Standard Make?)

-David
--
QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.



Bill Caroselli

Re: Debugging problems in 6.2.1a

Post by Bill Caroselli » Fri Aug 08, 2003 12:38 pm

128 MB may sound like a lot. But RTP eats those little bytes for
breakfast. Load as much of the system as you can then do a:
pidin in
What does the top line say after "FreeMem:"?


"Rdiger Loos" <Ruediger.Loos@3soft.de> wrote:
RdL > No Mikhail, it does not.
RdL > This happens with every single application trying to debug.
RdL > I have 128MB RAM on my target and I can't debug a "hello world" program :-(

RdL > Rdiger

RdL > "Mikhail Khodjaiants" <mikhailk@qnx.com> schrieb im Newsbeitrag
RdL > news:bgtqdo$je3$1@nntp.qnx.com...
It seems that your target is running out of memory.

Mikhail

Rüdiger Loos

Re: Debugging problems in 6.2.1a

Post by Rüdiger Loos » Fri Aug 08, 2003 2:36 pm

the top line says: FreeMem: FreeMem:7540Kb/16Mb
that should be enough for a "helo world" program I think.

"Bill Caroselli" <qtps@earthlink.net> schrieb im Newsbeitrag
news:bh05jp$9j9$1@inn.qnx.com...
128 MB may sound like a lot. But RTP eats those little bytes for
breakfast. Load as much of the system as you can then do a:
pidin in
What does the top line say after "FreeMem:"?


"Rdiger Loos" <Ruediger.Loos@3soft.de> wrote:
RdL > No Mikhail, it does not.
RdL > This happens with every single application trying to debug.
RdL > I have 128MB RAM on my target and I can't debug a "hello world"
program :-(

RdL > Rdiger

RdL > "Mikhail Khodjaiants" <mikhailk@qnx.com> schrieb im Newsbeitrag
RdL > news:bgtqdo$je3$1@nntp.qnx.com...
It seems that your target is running out of memory.

Mikhail

Alex Chapiro

Re: Debugging problems in 6.2.1a

Post by Alex Chapiro » Fri Aug 08, 2003 2:42 pm

Do you have /tmp linked to /dev/shmem? If so, how much space it uses
currently? It can easily exhaust your target memory.

Alex Chapiro

"Rüdiger Loos" <Ruediger.Loos@3SOFT.de> wrote in message
news:bgvo77$9m$1@inn.qnx.com...
No Mikhail, it does not.
This happens with every single application trying to debug.
I have 128MB RAM on my target and I can't debug a "hello world" program
:-(

Rüdiger

"Mikhail Khodjaiants" <mikhailk@qnx.com> schrieb im Newsbeitrag
news:bgtqdo$je3$1@nntp.qnx.com...
It seems that your target is running out of memory.

Mikhail

"Rüdiger Loos" <Ruediger.Loos@3SOFT.de> wrote in message
news:bgt56j$3o5$1@inn.qnx.com...
Hallo David,

I think the important entries are:

--------------------------
!ENTRY org.eclipse.debug.ui 4 120 Jun 17, 2003 12:47:13.220
!MESSAGE Error logged from Debug UI:
!STACK 1
org.eclipse.core.runtime.CoreException[503]: java.io.IOException: Open
Not
enough memory
at



com.qnx.tools.utils.target.TargetServiceFile.connect(TargetServiceFile.java:
347)
at



com.qnx.tools.utils.target.TargetServiceFile.creat(TargetServiceFile.java:24
3)
at



com.qnx.tools.utils.target.TargetFileDownload.download(TargetFileDownload.ja
va:54)
at



com.qnx.tools.ide.qde.internal.ui.launch.LaunchConfigurationDelegate.perform
FileTransfer(LaunchConfigurationDelegate.java:443)
at



com.qnx.tools.ide.qde.internal.ui.launch.LaunchConfigurationDelegate.launch(
LaunchConfigurationDelegate.java:144)
at



org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigurati
on.java:136)
at



org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationDialog
$10.run(LaunchConfigurationDialog.java:2299)
at



org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext
.java:98)
!ENTRY com.qnx.tools.ide.qde.ui 4 503 Jun 17, 2003 12:47:13.220
!MESSAGE Can't transfer file for etx : Open Not enough memory
!STACK 0
java.io.IOException: Open Not enough memory
at



com.qnx.tools.utils.target.TargetServiceFile.connect(TargetServiceFile.java:
347)
at



com.qnx.tools.utils.target.TargetServiceFile.creat(TargetServiceFile.java:24
3)
at



com.qnx.tools.utils.target.TargetFileDownload.download(TargetFileDownload.ja
va:54)
at



com.qnx.tools.ide.qde.internal.ui.launch.LaunchConfigurationDelegate.perform
FileTransfer(LaunchConfigurationDelegate.java:443)
at



com.qnx.tools.ide.qde.internal.ui.launch.LaunchConfigurationDelegate.launch(
LaunchConfigurationDelegate.java:144)
at



org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigurati
on.java:136)
at



org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationDialog
$10.run(LaunchConfigurationDialog.java:2299)
at



org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext
.java:98)
-------

and

-------
!ENTRY org.eclipse.debug.ui 4 120 Apr 07, 2003 15:13:49.875
!MESSAGE Error logged from Debug UI:
!STACK 1
org.eclipse.core.runtime.CoreException[150]: java.io.IOException: Exec
error:Launching failed
at org.eclipse.cdt.utils.spawner.Spawner.exec(Spawner.java:215)
at org.eclipse.cdt.utils.spawner.Spawner.<init>(Spawner.java:48)
at

org.eclipse.cdt.utils.spawner.ProcessFactory.exec(ProcessFactory.java:70)
at



org.eclipse.cdt.launch.internal.LocalCLaunchConfigurationDelegate.exec(Local
CLaunchConfigurationDelegate.java:213)
at



org.eclipse.cdt.launch.internal.LocalCLaunchConfigurationDelegate.launch(Loc
alCLaunchConfigurationDelegate.java:138)
at



org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigurati
on.java:136)
at



org.eclipse.debug.internal.ui.actions.RelaunchActionDelegate.relaunch(Relaun
chActionDelegate.java:56)
at



org.eclipse.debug.internal.ui.actions.RelaunchActionDelegate.relaunch(Relaun
chActionDelegate.java:32)
at



org.eclipse.debug.internal.ui.actions.RelaunchHistoryLaunchAction$1.run(Rela
unchHistoryLaunchAction.java:59)
at
org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:66)
at



org.eclipse.debug.internal.ui.actions.RelaunchHistoryLaunchAction.run(Relaun
chHistoryLaunchAction.java:57)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:749)
at



org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(Action
ContributionItem.java:407)
at



org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent(ActionCont
ributionItem.java:361)
at



org.eclipse.jface.action.ActionContributionItem.access$0(ActionContributionI
tem.java:352)
at



org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent(A
ctionContributionItem.java:47)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:77)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:827)
at
org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:1529)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1291)
at
org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1343)
at org.eclipse.ui.internal.Workbench.run(Workbench.java:1326)
at



org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.jav
a:831)
at org.eclipse.core.boot.BootLoader.run(BootLoader.java:462)
at java.lang.reflect.Method.invoke(Native Method)
at org.eclipse.core.launcher.Main.basicRun(Main.java:247)
at org.eclipse.core.launcher.Main.run(Main.java:703)
at org.eclipse.core.launcher.Main.main(Main.java:539)
-----

My momentics is running on a Windows XP PC an connected via Ethernet
with
my
X86 target.

The type of project is a "QNX C Application Project".

Regards

Rüdiger

P.S. I've heard of a patchB for Momentics 6.2.1 that should solve the
problem?!?


"David Gibbs" <dagibbs@qnx.com> schrieb im Newsbeitrag
news:bgrblu$j0n$2@nntp.qnx.com...
"Ruediger Loos" <Ruediger.Loos@3soft.de> wrote:
Hallo,

I have a big problem in debugging my QNX application.
I build my apps without any error and warning.
But when I start to debug my apps, I get a "Launch Configuration
Error"
with
one of the following informations:
"Exception occured processing launch configuration. Reason: Failed
Launching
CDI Debugger: Error initializing: Exec error:Launching failed" or
"Exception occured : Not enough memory"

Can anybody help me.

There's probably a .log file generated in workspace/.metadata, can
you
post the corresponding entry?

Also, what host are you running on?

Are you out of/low on system memory?

What type of project is it? (QNX C/C++? Standard Make?)

-David
--
QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.





Rüdiger Loos

Re: Debugging problems in 6.2.1a

Post by Rüdiger Loos » Fri Aug 08, 2003 2:45 pm

Hi Alex,

yes I've linked /tmp to /dev/shmem. But the space used does not exceed
128kB.

Rüdiger

"Alex Chapiro" <achapiro@qnx.com> schrieb im Newsbeitrag
news:bh0bkt$e1p$1@inn.qnx.com...
Do you have /tmp linked to /dev/shmem? If so, how much space it uses
currently? It can easily exhaust your target memory.

Alex Chapiro

"Rüdiger Loos" <Ruediger.Loos@3SOFT.de> wrote in message
news:bgvo77$9m$1@inn.qnx.com...
No Mikhail, it does not.
This happens with every single application trying to debug.
I have 128MB RAM on my target and I can't debug a "hello world" program
:-(

Rüdiger

"Mikhail Khodjaiants" <mikhailk@qnx.com> schrieb im Newsbeitrag
news:bgtqdo$je3$1@nntp.qnx.com...
It seems that your target is running out of memory.

Mikhail

"Rüdiger Loos" <Ruediger.Loos@3SOFT.de> wrote in message
news:bgt56j$3o5$1@inn.qnx.com...
Hallo David,

I think the important entries are:

--------------------------
!ENTRY org.eclipse.debug.ui 4 120 Jun 17, 2003 12:47:13.220
!MESSAGE Error logged from Debug UI:
!STACK 1
org.eclipse.core.runtime.CoreException[503]: java.io.IOException:
Open
Not
enough memory
at




com.qnx.tools.utils.target.TargetServiceFile.connect(TargetServiceFile.java:
347)
at




com.qnx.tools.utils.target.TargetServiceFile.creat(TargetServiceFile.java:24
3)
at




com.qnx.tools.utils.target.TargetFileDownload.download(TargetFileDownload.ja
va:54)
at




com.qnx.tools.ide.qde.internal.ui.launch.LaunchConfigurationDelegate.perform
FileTransfer(LaunchConfigurationDelegate.java:443)
at




com.qnx.tools.ide.qde.internal.ui.launch.LaunchConfigurationDelegate.launch(
LaunchConfigurationDelegate.java:144)
at




org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigurati
on.java:136)
at




org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationDialog
$10.run(LaunchConfigurationDialog.java:2299)
at




org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext
.java:98)
!ENTRY com.qnx.tools.ide.qde.ui 4 503 Jun 17, 2003 12:47:13.220
!MESSAGE Can't transfer file for etx : Open Not enough memory
!STACK 0
java.io.IOException: Open Not enough memory
at




com.qnx.tools.utils.target.TargetServiceFile.connect(TargetServiceFile.java:
347)
at




com.qnx.tools.utils.target.TargetServiceFile.creat(TargetServiceFile.java:24
3)
at




com.qnx.tools.utils.target.TargetFileDownload.download(TargetFileDownload.ja
va:54)
at




com.qnx.tools.ide.qde.internal.ui.launch.LaunchConfigurationDelegate.perform
FileTransfer(LaunchConfigurationDelegate.java:443)
at




com.qnx.tools.ide.qde.internal.ui.launch.LaunchConfigurationDelegate.launch(
LaunchConfigurationDelegate.java:144)
at




org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigurati
on.java:136)
at




org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationDialog
$10.run(LaunchConfigurationDialog.java:2299)
at




org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext
.java:98)
-------

and

-------
!ENTRY org.eclipse.debug.ui 4 120 Apr 07, 2003 15:13:49.875
!MESSAGE Error logged from Debug UI:
!STACK 1
org.eclipse.core.runtime.CoreException[150]: java.io.IOException:
Exec
error:Launching failed
at org.eclipse.cdt.utils.spawner.Spawner.exec(Spawner.java:215)
at org.eclipse.cdt.utils.spawner.Spawner.<init>(Spawner.java:48)
at


org.eclipse.cdt.utils.spawner.ProcessFactory.exec(ProcessFactory.java:70)
at




org.eclipse.cdt.launch.internal.LocalCLaunchConfigurationDelegate.exec(Local
CLaunchConfigurationDelegate.java:213)
at




org.eclipse.cdt.launch.internal.LocalCLaunchConfigurationDelegate.launch(Loc
alCLaunchConfigurationDelegate.java:138)
at




org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigurati
on.java:136)
at




org.eclipse.debug.internal.ui.actions.RelaunchActionDelegate.relaunch(Relaun
chActionDelegate.java:56)
at




org.eclipse.debug.internal.ui.actions.RelaunchActionDelegate.relaunch(Relaun
chActionDelegate.java:32)
at




org.eclipse.debug.internal.ui.actions.RelaunchHistoryLaunchAction$1.run(Rela
unchHistoryLaunchAction.java:59)
at
org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:66)
at




org.eclipse.debug.internal.ui.actions.RelaunchHistoryLaunchAction.run(Relaun
chHistoryLaunchAction.java:57)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:749)
at




org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(Action
ContributionItem.java:407)
at




org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent(ActionCont
ributionItem.java:361)
at




org.eclipse.jface.action.ActionContributionItem.access$0(ActionContributionI
tem.java:352)
at




org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent(A
ctionContributionItem.java:47)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:77)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:827)
at
org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:1529)
at
org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1291)
at
org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1343)
at org.eclipse.ui.internal.Workbench.run(Workbench.java:1326)
at




org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.jav
a:831)
at org.eclipse.core.boot.BootLoader.run(BootLoader.java:462)
at java.lang.reflect.Method.invoke(Native Method)
at org.eclipse.core.launcher.Main.basicRun(Main.java:247)
at org.eclipse.core.launcher.Main.run(Main.java:703)
at org.eclipse.core.launcher.Main.main(Main.java:539)
-----

My momentics is running on a Windows XP PC an connected via Ethernet
with
my
X86 target.

The type of project is a "QNX C Application Project".

Regards

Rüdiger

P.S. I've heard of a patchB for Momentics 6.2.1 that should solve
the
problem?!?


"David Gibbs" <dagibbs@qnx.com> schrieb im Newsbeitrag
news:bgrblu$j0n$2@nntp.qnx.com...
"Ruediger Loos" <Ruediger.Loos@3soft.de> wrote:
Hallo,

I have a big problem in debugging my QNX application.
I build my apps without any error and warning.
But when I start to debug my apps, I get a "Launch Configuration
Error"
with
one of the following informations:
"Exception occured processing launch configuration. Reason:
Failed
Launching
CDI Debugger: Error initializing: Exec error:Launching failed"
or
"Exception occured : Not enough memory"

Can anybody help me.

There's probably a .log file generated in workspace/.metadata, can
you
post the corresponding entry?

Also, what host are you running on?

Are you out of/low on system memory?

What type of project is it? (QNX C/C++? Standard Make?)

-David
--
QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.







Alex Chapiro

Re: Debugging problems in 6.2.1a

Post by Alex Chapiro » Fri Aug 08, 2003 3:30 pm

According to your log report, exception occurs while transferring file from
host to target. Exception message is just an errno description. Could you
please try to copy the same file from host to /tmp on target, using File
System Navigator?

"Rüdiger Loos" <Ruediger.Loos@3SOFT.de> wrote in message
news:bh0cdg$el9$1@inn.qnx.com...
Hi Alex,

yes I've linked /tmp to /dev/shmem. But the space used does not exceed
128kB.

Rüdiger

"Alex Chapiro" <achapiro@qnx.com> schrieb im Newsbeitrag
news:bh0bkt$e1p$1@inn.qnx.com...
Do you have /tmp linked to /dev/shmem? If so, how much space it uses
currently? It can easily exhaust your target memory.

Alex Chapiro

"Rüdiger Loos" <Ruediger.Loos@3SOFT.de> wrote in message
news:bgvo77$9m$1@inn.qnx.com...
No Mikhail, it does not.
This happens with every single application trying to debug.
I have 128MB RAM on my target and I can't debug a "hello world"
program
:-(

Rüdiger

"Mikhail Khodjaiants" <mikhailk@qnx.com> schrieb im Newsbeitrag
news:bgtqdo$je3$1@nntp.qnx.com...
It seems that your target is running out of memory.

Mikhail

"Rüdiger Loos" <Ruediger.Loos@3SOFT.de> wrote in message
news:bgt56j$3o5$1@inn.qnx.com...
Hallo David,

I think the important entries are:

--------------------------
!ENTRY org.eclipse.debug.ui 4 120 Jun 17, 2003 12:47:13.220
!MESSAGE Error logged from Debug UI:
!STACK 1
org.eclipse.core.runtime.CoreException[503]: java.io.IOException:
Open
Not
enough memory
at





com.qnx.tools.utils.target.TargetServiceFile.connect(TargetServiceFile.java:
347)
at





com.qnx.tools.utils.target.TargetServiceFile.creat(TargetServiceFile.java:24
3)
at





com.qnx.tools.utils.target.TargetFileDownload.download(TargetFileDownload.ja
va:54)
at





com.qnx.tools.ide.qde.internal.ui.launch.LaunchConfigurationDelegate.perform
FileTransfer(LaunchConfigurationDelegate.java:443)
at





com.qnx.tools.ide.qde.internal.ui.launch.LaunchConfigurationDelegate.launch(
LaunchConfigurationDelegate.java:144)
at





org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigurati
on.java:136)
at





org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationDialog
$10.run(LaunchConfigurationDialog.java:2299)
at





org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext
.java:98)
!ENTRY com.qnx.tools.ide.qde.ui 4 503 Jun 17, 2003 12:47:13.220
!MESSAGE Can't transfer file for etx : Open Not enough memory
!STACK 0
java.io.IOException: Open Not enough memory
at





com.qnx.tools.utils.target.TargetServiceFile.connect(TargetServiceFile.java:
347)
at





com.qnx.tools.utils.target.TargetServiceFile.creat(TargetServiceFile.java:24
3)
at





com.qnx.tools.utils.target.TargetFileDownload.download(TargetFileDownload.ja
va:54)
at





com.qnx.tools.ide.qde.internal.ui.launch.LaunchConfigurationDelegate.perform
FileTransfer(LaunchConfigurationDelegate.java:443)
at





com.qnx.tools.ide.qde.internal.ui.launch.LaunchConfigurationDelegate.launch(
LaunchConfigurationDelegate.java:144)
at





org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigurati
on.java:136)
at





org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationDialog
$10.run(LaunchConfigurationDialog.java:2299)
at





org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext
.java:98)
-------

and

-------
!ENTRY org.eclipse.debug.ui 4 120 Apr 07, 2003 15:13:49.875
!MESSAGE Error logged from Debug UI:
!STACK 1
org.eclipse.core.runtime.CoreException[150]: java.io.IOException:
Exec
error:Launching failed
at org.eclipse.cdt.utils.spawner.Spawner.exec(Spawner.java:215)
at org.eclipse.cdt.utils.spawner.Spawner.<init>(Spawner.java:48)
at


org.eclipse.cdt.utils.spawner.ProcessFactory.exec(ProcessFactory.java:70)
at





org.eclipse.cdt.launch.internal.LocalCLaunchConfigurationDelegate.exec(Local
CLaunchConfigurationDelegate.java:213)
at





org.eclipse.cdt.launch.internal.LocalCLaunchConfigurationDelegate.launch(Loc
alCLaunchConfigurationDelegate.java:138)
at





org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigurati
on.java:136)
at





org.eclipse.debug.internal.ui.actions.RelaunchActionDelegate.relaunch(Relaun
chActionDelegate.java:56)
at





org.eclipse.debug.internal.ui.actions.RelaunchActionDelegate.relaunch(Relaun
chActionDelegate.java:32)
at





org.eclipse.debug.internal.ui.actions.RelaunchHistoryLaunchAction$1.run(Rela
unchHistoryLaunchAction.java:59)
at
org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:66)
at





org.eclipse.debug.internal.ui.actions.RelaunchHistoryLaunchAction.run(Relaun
chHistoryLaunchAction.java:57)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:749)
at





org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(Action
ContributionItem.java:407)
at





org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent(ActionCont
ributionItem.java:361)
at





org.eclipse.jface.action.ActionContributionItem.access$0(ActionContributionI
tem.java:352)
at





org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent(A
ctionContributionItem.java:47)
at
org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:77)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:827)
at
org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:1529)
at
org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1291)
at
org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1343)
at org.eclipse.ui.internal.Workbench.run(Workbench.java:1326)
at





org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.jav
a:831)
at org.eclipse.core.boot.BootLoader.run(BootLoader.java:462)
at java.lang.reflect.Method.invoke(Native Method)
at org.eclipse.core.launcher.Main.basicRun(Main.java:247)
at org.eclipse.core.launcher.Main.run(Main.java:703)
at org.eclipse.core.launcher.Main.main(Main.java:539)
-----

My momentics is running on a Windows XP PC an connected via
Ethernet
with
my
X86 target.

The type of project is a "QNX C Application Project".

Regards

Rüdiger

P.S. I've heard of a patchB for Momentics 6.2.1 that should solve
the
problem?!?


"David Gibbs" <dagibbs@qnx.com> schrieb im Newsbeitrag
news:bgrblu$j0n$2@nntp.qnx.com...
"Ruediger Loos" <Ruediger.Loos@3soft.de> wrote:
Hallo,

I have a big problem in debugging my QNX application.
I build my apps without any error and warning.
But when I start to debug my apps, I get a "Launch
Configuration
Error"
with
one of the following informations:
"Exception occured processing launch configuration. Reason:
Failed
Launching
CDI Debugger: Error initializing: Exec error:Launching failed"
or
"Exception occured : Not enough memory"

Can anybody help me.

There's probably a .log file generated in workspace/.metadata,
can
you
post the corresponding entry?

Also, what host are you running on?

Are you out of/low on system memory?

What type of project is it? (QNX C/C++? Standard Make?)

-David
--
QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.









Rüdiger Loos

Re: Debugging problems in 6.2.1a

Post by Rüdiger Loos » Mon Aug 11, 2003 9:21 am

I have no problem transfering the file from host to target using file system
navigator. Even larger files (10MB instead of 470kB) can be transfered
without any problem.

"Alex Chapiro" <achapiro@qnx.com> schrieb im Newsbeitrag
news:bh0edt$g2t$1@inn.qnx.com...
According to your log report, exception occurs while transferring file
from
host to target. Exception message is just an errno description. Could you
please try to copy the same file from host to /tmp on target, using File
System Navigator?

"Rüdiger Loos" <Ruediger.Loos@3SOFT.de> wrote in message
news:bh0cdg$el9$1@inn.qnx.com...
Hi Alex,

yes I've linked /tmp to /dev/shmem. But the space used does not exceed
128kB.

Rüdiger

"Alex Chapiro" <achapiro@qnx.com> schrieb im Newsbeitrag
news:bh0bkt$e1p$1@inn.qnx.com...
Do you have /tmp linked to /dev/shmem? If so, how much space it uses
currently? It can easily exhaust your target memory.

Alex Chapiro

"Rüdiger Loos" <Ruediger.Loos@3SOFT.de> wrote in message
news:bgvo77$9m$1@inn.qnx.com...
No Mikhail, it does not.
This happens with every single application trying to debug.
I have 128MB RAM on my target and I can't debug a "hello world"
program
:-(

Rüdiger

"Mikhail Khodjaiants" <mikhailk@qnx.com> schrieb im Newsbeitrag
news:bgtqdo$je3$1@nntp.qnx.com...
It seems that your target is running out of memory.

Mikhail

"Rüdiger Loos" <Ruediger.Loos@3SOFT.de> wrote in message
news:bgt56j$3o5$1@inn.qnx.com...
Hallo David,

I think the important entries are:

--------------------------
!ENTRY org.eclipse.debug.ui 4 120 Jun 17, 2003 12:47:13.220
!MESSAGE Error logged from Debug UI:
!STACK 1
org.eclipse.core.runtime.CoreException[503]:
java.io.IOException:
Open
Not
enough memory
at






com.qnx.tools.utils.target.TargetServiceFile.connect(TargetServiceFile.java:
347)
at






com.qnx.tools.utils.target.TargetServiceFile.creat(TargetServiceFile.java:24
3)
at






com.qnx.tools.utils.target.TargetFileDownload.download(TargetFileDownload.ja
va:54)
at






com.qnx.tools.ide.qde.internal.ui.launch.LaunchConfigurationDelegate.perform
FileTransfer(LaunchConfigurationDelegate.java:443)
at






com.qnx.tools.ide.qde.internal.ui.launch.LaunchConfigurationDelegate.launch(
LaunchConfigurationDelegate.java:144)
at






org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigurati
on.java:136)
at






org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationDialog
$10.run(LaunchConfigurationDialog.java:2299)
at






org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext
.java:98)
!ENTRY com.qnx.tools.ide.qde.ui 4 503 Jun 17, 2003 12:47:13.220
!MESSAGE Can't transfer file for etx : Open Not enough memory
!STACK 0
java.io.IOException: Open Not enough memory
at






com.qnx.tools.utils.target.TargetServiceFile.connect(TargetServiceFile.java:
347)
at






com.qnx.tools.utils.target.TargetServiceFile.creat(TargetServiceFile.java:24
3)
at






com.qnx.tools.utils.target.TargetFileDownload.download(TargetFileDownload.ja
va:54)
at






com.qnx.tools.ide.qde.internal.ui.launch.LaunchConfigurationDelegate.perform
FileTransfer(LaunchConfigurationDelegate.java:443)
at






com.qnx.tools.ide.qde.internal.ui.launch.LaunchConfigurationDelegate.launch(
LaunchConfigurationDelegate.java:144)
at






org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigurati
on.java:136)
at






org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationDialog
$10.run(LaunchConfigurationDialog.java:2299)
at






org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext
.java:98)
-------

and

-------
!ENTRY org.eclipse.debug.ui 4 120 Apr 07, 2003 15:13:49.875
!MESSAGE Error logged from Debug UI:
!STACK 1
org.eclipse.core.runtime.CoreException[150]:
java.io.IOException:
Exec
error:Launching failed
at org.eclipse.cdt.utils.spawner.Spawner.exec(Spawner.java:215)
at
org.eclipse.cdt.utils.spawner.Spawner.<init>(Spawner.java:48)
at



org.eclipse.cdt.utils.spawner.ProcessFactory.exec(ProcessFactory.java:70)
at






org.eclipse.cdt.launch.internal.LocalCLaunchConfigurationDelegate.exec(Local
CLaunchConfigurationDelegate.java:213)
at






org.eclipse.cdt.launch.internal.LocalCLaunchConfigurationDelegate.launch(Loc
alCLaunchConfigurationDelegate.java:138)
at






org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigurati
on.java:136)
at






org.eclipse.debug.internal.ui.actions.RelaunchActionDelegate.relaunch(Relaun
chActionDelegate.java:56)
at






org.eclipse.debug.internal.ui.actions.RelaunchActionDelegate.relaunch(Relaun
chActionDelegate.java:32)
at






org.eclipse.debug.internal.ui.actions.RelaunchHistoryLaunchAction$1.run(Rela
unchHistoryLaunchAction.java:59)
at

org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:66)
at






org.eclipse.debug.internal.ui.actions.RelaunchHistoryLaunchAction.run(Relaun
chHistoryLaunchAction.java:57)
at
org.eclipse.jface.action.Action.runWithEvent(Action.java:749)
at






org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(Action
ContributionItem.java:407)
at






org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent(ActionCont
ributionItem.java:361)
at






org.eclipse.jface.action.ActionContributionItem.access$0(ActionContributionI
tem.java:352)
at






org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent(A
ctionContributionItem.java:47)
at
org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:77)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:827)
at
org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:1529)
at
org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1291)
at
org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1343)
at org.eclipse.ui.internal.Workbench.run(Workbench.java:1326)
at






org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.jav
a:831)
at org.eclipse.core.boot.BootLoader.run(BootLoader.java:462)
at java.lang.reflect.Method.invoke(Native Method)
at org.eclipse.core.launcher.Main.basicRun(Main.java:247)
at org.eclipse.core.launcher.Main.run(Main.java:703)
at org.eclipse.core.launcher.Main.main(Main.java:539)
-----

My momentics is running on a Windows XP PC an connected via
Ethernet
with
my
X86 target.

The type of project is a "QNX C Application Project".

Regards

Rüdiger

P.S. I've heard of a patchB for Momentics 6.2.1 that should
solve
the
problem?!?


"David Gibbs" <dagibbs@qnx.com> schrieb im Newsbeitrag
news:bgrblu$j0n$2@nntp.qnx.com...
"Ruediger Loos" <Ruediger.Loos@3soft.de> wrote:
Hallo,

I have a big problem in debugging my QNX application.
I build my apps without any error and warning.
But when I start to debug my apps, I get a "Launch
Configuration
Error"
with
one of the following informations:
"Exception occured processing launch configuration. Reason:
Failed
Launching
CDI Debugger: Error initializing: Exec error:Launching
failed"
or
"Exception occured : Not enough memory"

Can anybody help me.

There's probably a .log file generated in workspace/.metadata,
can
you
post the corresponding entry?

Also, what host are you running on?

Are you out of/low on system memory?

What type of project is it? (QNX C/C++? Standard Make?)

-David
--
QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further
questions.











Alex Chapiro

Re: Debugging problems in 6.2.1a

Post by Alex Chapiro » Mon Aug 11, 2003 5:27 pm

Things keep getting to be more and more weird.:-))). I guess before
continuing of this issue investigation it is a good time to ask you which
version are you using on your host and on your target? Host build version
you can find in about dialog. As far as I remember, we never shipped 6.2.1A.
This is important to know in order to look at correct code.

Alex Chapiro


"Rüdiger Loos" <Ruediger.Loos@3SOFT.de> wrote in message
news:bh7mhp$mpr$1@inn.qnx.com...
I have no problem transfering the file from host to target using file
system
navigator. Even larger files (10MB instead of 470kB) can be transfered
without any problem.

"Alex Chapiro" <achapiro@qnx.com> schrieb im Newsbeitrag
news:bh0edt$g2t$1@inn.qnx.com...
According to your log report, exception occurs while transferring file
from
host to target. Exception message is just an errno description. Could
you
please try to copy the same file from host to /tmp on target, using File
System Navigator?

"Rüdiger Loos" <Ruediger.Loos@3SOFT.de> wrote in message
news:bh0cdg$el9$1@inn.qnx.com...
Hi Alex,

yes I've linked /tmp to /dev/shmem. But the space used does not exceed
128kB.

Rüdiger

"Alex Chapiro" <achapiro@qnx.com> schrieb im Newsbeitrag
news:bh0bkt$e1p$1@inn.qnx.com...
Do you have /tmp linked to /dev/shmem? If so, how much space it uses
currently? It can easily exhaust your target memory.

Alex Chapiro

"Rüdiger Loos" <Ruediger.Loos@3SOFT.de> wrote in message
news:bgvo77$9m$1@inn.qnx.com...
No Mikhail, it does not.
This happens with every single application trying to debug.
I have 128MB RAM on my target and I can't debug a "hello world"
program
:-(

Rüdiger

"Mikhail Khodjaiants" <mikhailk@qnx.com> schrieb im Newsbeitrag
news:bgtqdo$je3$1@nntp.qnx.com...
It seems that your target is running out of memory.

Mikhail

"Rüdiger Loos" <Ruediger.Loos@3SOFT.de> wrote in message
news:bgt56j$3o5$1@inn.qnx.com...
Hallo David,

I think the important entries are:

--------------------------
!ENTRY org.eclipse.debug.ui 4 120 Jun 17, 2003 12:47:13.220
!MESSAGE Error logged from Debug UI:
!STACK 1
org.eclipse.core.runtime.CoreException[503]:
java.io.IOException:
Open
Not
enough memory
at







com.qnx.tools.utils.target.TargetServiceFile.connect(TargetServiceFile.java:
347)
at







com.qnx.tools.utils.target.TargetServiceFile.creat(TargetServiceFile.java:24
3)
at







com.qnx.tools.utils.target.TargetFileDownload.download(TargetFileDownload.ja
va:54)
at







com.qnx.tools.ide.qde.internal.ui.launch.LaunchConfigurationDelegate.perform
FileTransfer(LaunchConfigurationDelegate.java:443)
at







com.qnx.tools.ide.qde.internal.ui.launch.LaunchConfigurationDelegate.launch(
LaunchConfigurationDelegate.java:144)
at







org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigurati
on.java:136)
at







org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationDialog
$10.run(LaunchConfigurationDialog.java:2299)
at







org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext
.java:98)
!ENTRY com.qnx.tools.ide.qde.ui 4 503 Jun 17, 2003
12:47:13.220
!MESSAGE Can't transfer file for etx : Open Not enough memory
!STACK 0
java.io.IOException: Open Not enough memory
at







com.qnx.tools.utils.target.TargetServiceFile.connect(TargetServiceFile.java:
347)
at







com.qnx.tools.utils.target.TargetServiceFile.creat(TargetServiceFile.java:24
3)
at







com.qnx.tools.utils.target.TargetFileDownload.download(TargetFileDownload.ja
va:54)
at







com.qnx.tools.ide.qde.internal.ui.launch.LaunchConfigurationDelegate.perform
FileTransfer(LaunchConfigurationDelegate.java:443)
at







com.qnx.tools.ide.qde.internal.ui.launch.LaunchConfigurationDelegate.launch(
LaunchConfigurationDelegate.java:144)
at







org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigurati
on.java:136)
at







org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationDialog
$10.run(LaunchConfigurationDialog.java:2299)
at







org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext
.java:98)
-------

and

-------
!ENTRY org.eclipse.debug.ui 4 120 Apr 07, 2003 15:13:49.875
!MESSAGE Error logged from Debug UI:
!STACK 1
org.eclipse.core.runtime.CoreException[150]:
java.io.IOException:
Exec
error:Launching failed
at
org.eclipse.cdt.utils.spawner.Spawner.exec(Spawner.java:215)
at
org.eclipse.cdt.utils.spawner.Spawner.<init>(Spawner.java:48)
at



org.eclipse.cdt.utils.spawner.ProcessFactory.exec(ProcessFactory.java:70)
at







org.eclipse.cdt.launch.internal.LocalCLaunchConfigurationDelegate.exec(Local
CLaunchConfigurationDelegate.java:213)
at







org.eclipse.cdt.launch.internal.LocalCLaunchConfigurationDelegate.launch(Loc
alCLaunchConfigurationDelegate.java:138)
at







org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigurati
on.java:136)
at







org.eclipse.debug.internal.ui.actions.RelaunchActionDelegate.relaunch(Relaun
chActionDelegate.java:56)
at







org.eclipse.debug.internal.ui.actions.RelaunchActionDelegate.relaunch(Relaun
chActionDelegate.java:32)
at







org.eclipse.debug.internal.ui.actions.RelaunchHistoryLaunchAction$1.run(Rela
unchHistoryLaunchAction.java:59)
at

org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:66)
at







org.eclipse.debug.internal.ui.actions.RelaunchHistoryLaunchAction.run(Relaun
chHistoryLaunchAction.java:57)
at
org.eclipse.jface.action.Action.runWithEvent(Action.java:749)
at







org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(Action
ContributionItem.java:407)
at







org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent(ActionCont
ributionItem.java:361)
at







org.eclipse.jface.action.ActionContributionItem.access$0(ActionContributionI
tem.java:352)
at







org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent(A
ctionContributionItem.java:47)
at
org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:77)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:827)
at
org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:1529)
at
org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1291)
at
org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1343)
at org.eclipse.ui.internal.Workbench.run(Workbench.java:1326)
at







org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.jav
a:831)
at org.eclipse.core.boot.BootLoader.run(BootLoader.java:462)
at java.lang.reflect.Method.invoke(Native Method)
at org.eclipse.core.launcher.Main.basicRun(Main.java:247)
at org.eclipse.core.launcher.Main.run(Main.java:703)
at org.eclipse.core.launcher.Main.main(Main.java:539)
-----

My momentics is running on a Windows XP PC an connected via
Ethernet
with
my
X86 target.

The type of project is a "QNX C Application Project".

Regards

Rüdiger

P.S. I've heard of a patchB for Momentics 6.2.1 that should
solve
the
problem?!?


"David Gibbs" <dagibbs@qnx.com> schrieb im Newsbeitrag
news:bgrblu$j0n$2@nntp.qnx.com...
"Ruediger Loos" <Ruediger.Loos@3soft.de> wrote:
Hallo,

I have a big problem in debugging my QNX application.
I build my apps without any error and warning.
But when I start to debug my apps, I get a "Launch
Configuration
Error"
with
one of the following informations:
"Exception occured processing launch configuration.
Reason:
Failed
Launching
CDI Debugger: Error initializing: Exec error:Launching
failed"
or
"Exception occured : Not enough memory"

Can anybody help me.

There's probably a .log file generated in
workspace/.metadata,
can
you
post the corresponding entry?

Also, what host are you running on?

Are you out of/low on system memory?

What type of project is it? (QNX C/C++? Standard Make?)

-David
--
QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further
questions.













Rüdiger Loos

Re: Debugging problems in 6.2.1a

Post by Rüdiger Loos » Tue Aug 12, 2003 8:43 am

We definitely have version 6.2.1a installed on out host.
As I've heard from our customer, his/our target uses version 6.2.1, but we
don't know whether it is 6.2.1 or 6.2.1a.
When I have the target connected to my host, how can I determine the version
of the os installed on my target?

Thanks in advance
Rüdiger Loos

"Alex Chapiro" <achapiro@qnx.com> schrieb im Newsbeitrag
news:bh8ic0$ck9$1@inn.qnx.com...
Things keep getting to be more and more weird.:-))). I guess before
continuing of this issue investigation it is a good time to ask you which
version are you using on your host and on your target? Host build version
you can find in about dialog. As far as I remember, we never shipped
6.2.1A.
This is important to know in order to look at correct code.

Alex Chapiro


"Rüdiger Loos" <Ruediger.Loos@3SOFT.de> wrote in message
news:bh7mhp$mpr$1@inn.qnx.com...
I have no problem transfering the file from host to target using file
system
navigator. Even larger files (10MB instead of 470kB) can be transfered
without any problem.

"Alex Chapiro" <achapiro@qnx.com> schrieb im Newsbeitrag
news:bh0edt$g2t$1@inn.qnx.com...
According to your log report, exception occurs while transferring file
from
host to target. Exception message is just an errno description. Could
you
please try to copy the same file from host to /tmp on target, using
File
System Navigator?

"Rüdiger Loos" <Ruediger.Loos@3SOFT.de> wrote in message
news:bh0cdg$el9$1@inn.qnx.com...
Hi Alex,

yes I've linked /tmp to /dev/shmem. But the space used does not
exceed
128kB.

Rüdiger

"Alex Chapiro" <achapiro@qnx.com> schrieb im Newsbeitrag
news:bh0bkt$e1p$1@inn.qnx.com...
Do you have /tmp linked to /dev/shmem? If so, how much space it
uses
currently? It can easily exhaust your target memory.

Alex Chapiro

"Rüdiger Loos" <Ruediger.Loos@3SOFT.de> wrote in message
news:bgvo77$9m$1@inn.qnx.com...
No Mikhail, it does not.
This happens with every single application trying to debug.
I have 128MB RAM on my target and I can't debug a "hello world"
program
:-(

Rüdiger

"Mikhail Khodjaiants" <mikhailk@qnx.com> schrieb im Newsbeitrag
news:bgtqdo$je3$1@nntp.qnx.com...
It seems that your target is running out of memory.

Mikhail

"Rüdiger Loos" <Ruediger.Loos@3SOFT.de> wrote in message
news:bgt56j$3o5$1@inn.qnx.com...
Hallo David,

I think the important entries are:

--------------------------
!ENTRY org.eclipse.debug.ui 4 120 Jun 17, 2003 12:47:13.220
!MESSAGE Error logged from Debug UI:
!STACK 1
org.eclipse.core.runtime.CoreException[503]:
java.io.IOException:
Open
Not
enough memory
at








com.qnx.tools.utils.target.TargetServiceFile.connect(TargetServiceFile.java:
347)
at








com.qnx.tools.utils.target.TargetServiceFile.creat(TargetServiceFile.java:24
3)
at








com.qnx.tools.utils.target.TargetFileDownload.download(TargetFileDownload.ja
va:54)
at








com.qnx.tools.ide.qde.internal.ui.launch.LaunchConfigurationDelegate.perform
FileTransfer(LaunchConfigurationDelegate.java:443)
at








com.qnx.tools.ide.qde.internal.ui.launch.LaunchConfigurationDelegate.launch(
LaunchConfigurationDelegate.java:144)
at








org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigurati
on.java:136)
at








org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationDialog
$10.run(LaunchConfigurationDialog.java:2299)
at








org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext
.java:98)
!ENTRY com.qnx.tools.ide.qde.ui 4 503 Jun 17, 2003
12:47:13.220
!MESSAGE Can't transfer file for etx : Open Not enough
memory
!STACK 0
java.io.IOException: Open Not enough memory
at








com.qnx.tools.utils.target.TargetServiceFile.connect(TargetServiceFile.java:
347)
at








com.qnx.tools.utils.target.TargetServiceFile.creat(TargetServiceFile.java:24
3)
at








com.qnx.tools.utils.target.TargetFileDownload.download(TargetFileDownload.ja
va:54)
at








com.qnx.tools.ide.qde.internal.ui.launch.LaunchConfigurationDelegate.perform
FileTransfer(LaunchConfigurationDelegate.java:443)
at








com.qnx.tools.ide.qde.internal.ui.launch.LaunchConfigurationDelegate.launch(
LaunchConfigurationDelegate.java:144)
at








org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigurati
on.java:136)
at








org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationDialog
$10.run(LaunchConfigurationDialog.java:2299)
at








org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext
.java:98)
-------

and

-------
!ENTRY org.eclipse.debug.ui 4 120 Apr 07, 2003 15:13:49.875
!MESSAGE Error logged from Debug UI:
!STACK 1
org.eclipse.core.runtime.CoreException[150]:
java.io.IOException:
Exec
error:Launching failed
at
org.eclipse.cdt.utils.spawner.Spawner.exec(Spawner.java:215)
at
org.eclipse.cdt.utils.spawner.Spawner.<init>(Spawner.java:48)
at




org.eclipse.cdt.utils.spawner.ProcessFactory.exec(ProcessFactory.java:70)
at








org.eclipse.cdt.launch.internal.LocalCLaunchConfigurationDelegate.exec(Local
CLaunchConfigurationDelegate.java:213)
at








org.eclipse.cdt.launch.internal.LocalCLaunchConfigurationDelegate.launch(Loc
alCLaunchConfigurationDelegate.java:138)
at








org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigurati
on.java:136)
at








org.eclipse.debug.internal.ui.actions.RelaunchActionDelegate.relaunch(Relaun
chActionDelegate.java:56)
at








org.eclipse.debug.internal.ui.actions.RelaunchActionDelegate.relaunch(Relaun
chActionDelegate.java:32)
at








org.eclipse.debug.internal.ui.actions.RelaunchHistoryLaunchAction$1.run(Rela
unchHistoryLaunchAction.java:59)
at

org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:66)
at








org.eclipse.debug.internal.ui.actions.RelaunchHistoryLaunchAction.run(Relaun
chHistoryLaunchAction.java:57)
at
org.eclipse.jface.action.Action.runWithEvent(Action.java:749)
at








org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(Action
ContributionItem.java:407)
at








org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent(ActionCont
ributionItem.java:361)
at








org.eclipse.jface.action.ActionContributionItem.access$0(ActionContributionI
tem.java:352)
at








org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent(A
ctionContributionItem.java:47)
at
org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:77)
at
org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:827)
at

org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:1529)
at
org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1291)
at

org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1343)
at
org.eclipse.ui.internal.Workbench.run(Workbench.java:1326)
at








org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.jav
a:831)
at
org.eclipse.core.boot.BootLoader.run(BootLoader.java:462)
at java.lang.reflect.Method.invoke(Native Method)
at org.eclipse.core.launcher.Main.basicRun(Main.java:247)
at org.eclipse.core.launcher.Main.run(Main.java:703)
at org.eclipse.core.launcher.Main.main(Main.java:539)
-----

My momentics is running on a Windows XP PC an connected via
Ethernet
with
my
X86 target.

The type of project is a "QNX C Application Project".

Regards

Rüdiger

P.S. I've heard of a patchB for Momentics 6.2.1 that should
solve
the
problem?!?


"David Gibbs" <dagibbs@qnx.com> schrieb im Newsbeitrag
news:bgrblu$j0n$2@nntp.qnx.com...
"Ruediger Loos" <Ruediger.Loos@3soft.de> wrote:
Hallo,

I have a big problem in debugging my QNX application.
I build my apps without any error and warning.
But when I start to debug my apps, I get a "Launch
Configuration
Error"
with
one of the following informations:
"Exception occured processing launch configuration.
Reason:
Failed
Launching
CDI Debugger: Error initializing: Exec error:Launching
failed"
or
"Exception occured : Not enough memory"

Can anybody help me.

There's probably a .log file generated in
workspace/.metadata,
can
you
post the corresponding entry?

Also, what host are you running on?

Are you out of/low on system memory?

What type of project is it? (QNX C/C++? Standard Make?)

-David
--
QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further
questions.















Alex Chapiro

Re: Debugging problems in 6.2.1a

Post by Alex Chapiro » Tue Aug 12, 2003 12:09 pm

At least let me know Build ID from the About QNX Momentics IDE dialog.
For target please check the date of build for /usr/sbin/qconn.

"Rüdiger Loos" <Ruediger.Loos@3SOFT.de> wrote in message
news:bha8mq$je7$1@inn.qnx.com...
We definitely have version 6.2.1a installed on out host.
As I've heard from our customer, his/our target uses version 6.2.1, but we
don't know whether it is 6.2.1 or 6.2.1a.
When I have the target connected to my host, how can I determine the
version
of the os installed on my target?

Thanks in advance
Rüdiger Loos

"Alex Chapiro" <achapiro@qnx.com> schrieb im Newsbeitrag
news:bh8ic0$ck9$1@inn.qnx.com...
Things keep getting to be more and more weird.:-))). I guess before
continuing of this issue investigation it is a good time to ask you
which
version are you using on your host and on your target? Host build
version
you can find in about dialog. As far as I remember, we never shipped
6.2.1A.
This is important to know in order to look at correct code.

Alex Chapiro


"Rüdiger Loos" <Ruediger.Loos@3SOFT.de> wrote in message
news:bh7mhp$mpr$1@inn.qnx.com...
I have no problem transfering the file from host to target using file
system
navigator. Even larger files (10MB instead of 470kB) can be transfered
without any problem.

"Alex Chapiro" <achapiro@qnx.com> schrieb im Newsbeitrag
news:bh0edt$g2t$1@inn.qnx.com...
According to your log report, exception occurs while transferring
file
from
host to target. Exception message is just an errno description.
Could
you
please try to copy the same file from host to /tmp on target, using
File
System Navigator?

"Rüdiger Loos" <Ruediger.Loos@3SOFT.de> wrote in message
news:bh0cdg$el9$1@inn.qnx.com...
Hi Alex,

yes I've linked /tmp to /dev/shmem. But the space used does not
exceed
128kB.

Rüdiger

"Alex Chapiro" <achapiro@qnx.com> schrieb im Newsbeitrag
news:bh0bkt$e1p$1@inn.qnx.com...
Do you have /tmp linked to /dev/shmem? If so, how much space it
uses
currently? It can easily exhaust your target memory.

Alex Chapiro

"Rüdiger Loos" <Ruediger.Loos@3SOFT.de> wrote in message
news:bgvo77$9m$1@inn.qnx.com...
No Mikhail, it does not.
This happens with every single application trying to debug.
I have 128MB RAM on my target and I can't debug a "hello
world"
program
:-(

Rüdiger

"Mikhail Khodjaiants" <mikhailk@qnx.com> schrieb im
Newsbeitrag
news:bgtqdo$je3$1@nntp.qnx.com...
It seems that your target is running out of memory.

Mikhail

"Rüdiger Loos" <Ruediger.Loos@3SOFT.de> wrote in message
news:bgt56j$3o5$1@inn.qnx.com...
Hallo David,

I think the important entries are:

--------------------------
!ENTRY org.eclipse.debug.ui 4 120 Jun 17, 2003
12:47:13.220
!MESSAGE Error logged from Debug UI:
!STACK 1
org.eclipse.core.runtime.CoreException[503]:
java.io.IOException:
Open
Not
enough memory
at









com.qnx.tools.utils.target.TargetServiceFile.connect(TargetServiceFile.java:
347)
at









com.qnx.tools.utils.target.TargetServiceFile.creat(TargetServiceFile.java:24
3)
at









com.qnx.tools.utils.target.TargetFileDownload.download(TargetFileDownload.ja
va:54)
at









com.qnx.tools.ide.qde.internal.ui.launch.LaunchConfigurationDelegate.perform
FileTransfer(LaunchConfigurationDelegate.java:443)
at









com.qnx.tools.ide.qde.internal.ui.launch.LaunchConfigurationDelegate.launch(
LaunchConfigurationDelegate.java:144)
at









org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigurati
on.java:136)
at









org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationDialog
$10.run(LaunchConfigurationDialog.java:2299)
at









org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext
.java:98)
!ENTRY com.qnx.tools.ide.qde.ui 4 503 Jun 17, 2003
12:47:13.220
!MESSAGE Can't transfer file for etx : Open Not enough
memory
!STACK 0
java.io.IOException: Open Not enough memory
at









com.qnx.tools.utils.target.TargetServiceFile.connect(TargetServiceFile.java:
347)
at









com.qnx.tools.utils.target.TargetServiceFile.creat(TargetServiceFile.java:24
3)
at









com.qnx.tools.utils.target.TargetFileDownload.download(TargetFileDownload.ja
va:54)
at









com.qnx.tools.ide.qde.internal.ui.launch.LaunchConfigurationDelegate.perform
FileTransfer(LaunchConfigurationDelegate.java:443)
at









com.qnx.tools.ide.qde.internal.ui.launch.LaunchConfigurationDelegate.launch(
LaunchConfigurationDelegate.java:144)
at









org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigurati
on.java:136)
at









org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationDialog
$10.run(LaunchConfigurationDialog.java:2299)
at









org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext
.java:98)
-------

and

-------
!ENTRY org.eclipse.debug.ui 4 120 Apr 07, 2003
15:13:49.875
!MESSAGE Error logged from Debug UI:
!STACK 1
org.eclipse.core.runtime.CoreException[150]:
java.io.IOException:
Exec
error:Launching failed
at
org.eclipse.cdt.utils.spawner.Spawner.exec(Spawner.java:215)
at
org.eclipse.cdt.utils.spawner.Spawner.<init>(Spawner.java:48)
at




org.eclipse.cdt.utils.spawner.ProcessFactory.exec(ProcessFactory.java:70)
at









org.eclipse.cdt.launch.internal.LocalCLaunchConfigurationDelegate.exec(Local
CLaunchConfigurationDelegate.java:213)
at









org.eclipse.cdt.launch.internal.LocalCLaunchConfigurationDelegate.launch(Loc
alCLaunchConfigurationDelegate.java:138)
at









org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigurati
on.java:136)
at









org.eclipse.debug.internal.ui.actions.RelaunchActionDelegate.relaunch(Relaun
chActionDelegate.java:56)
at









org.eclipse.debug.internal.ui.actions.RelaunchActionDelegate.relaunch(Relaun
chActionDelegate.java:32)
at









org.eclipse.debug.internal.ui.actions.RelaunchHistoryLaunchAction$1.run(Rela
unchHistoryLaunchAction.java:59)
at

org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:66)
at









org.eclipse.debug.internal.ui.actions.RelaunchHistoryLaunchAction.run(Relaun
chHistoryLaunchAction.java:57)
at
org.eclipse.jface.action.Action.runWithEvent(Action.java:749)
at









org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(Action
ContributionItem.java:407)
at









org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent(ActionCont
ributionItem.java:361)
at









org.eclipse.jface.action.ActionContributionItem.access$0(ActionContributionI
tem.java:352)
at









org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent(A
ctionContributionItem.java:47)
at
org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:77)
at
org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:827)
at

org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:1529)
at
org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1291)
at

org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1343)
at
org.eclipse.ui.internal.Workbench.run(Workbench.java:1326)
at









org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.jav
a:831)
at
org.eclipse.core.boot.BootLoader.run(BootLoader.java:462)
at java.lang.reflect.Method.invoke(Native Method)
at org.eclipse.core.launcher.Main.basicRun(Main.java:247)
at org.eclipse.core.launcher.Main.run(Main.java:703)
at org.eclipse.core.launcher.Main.main(Main.java:539)
-----

My momentics is running on a Windows XP PC an connected
via
Ethernet
with
my
X86 target.

The type of project is a "QNX C Application Project".

Regards

Rüdiger

P.S. I've heard of a patchB for Momentics 6.2.1 that
should
solve
the
problem?!?


"David Gibbs" <dagibbs@qnx.com> schrieb im Newsbeitrag
news:bgrblu$j0n$2@nntp.qnx.com...
"Ruediger Loos" <Ruediger.Loos@3soft.de> wrote:
Hallo,

I have a big problem in debugging my QNX application.
I build my apps without any error and warning.
But when I start to debug my apps, I get a "Launch
Configuration
Error"
with
one of the following informations:
"Exception occured processing launch configuration.
Reason:
Failed
Launching
CDI Debugger: Error initializing: Exec error:Launching
failed"
or
"Exception occured : Not enough memory"

Can anybody help me.

There's probably a .log file generated in
workspace/.metadata,
can
you
post the corresponding entry?

Also, what host are you running on?

Are you out of/low on system memory?

What type of project is it? (QNX C/C++? Standard Make?)

-David
--
QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further
questions.

















Rüdiger Loos

Re: Debugging problems in 6.2.1a

Post by Rüdiger Loos » Tue Aug 12, 2003 3:36 pm

Having heard the patchB to 6.2.1b shall solve my problem I've installed the
patch. But, no way, I still have the same problem.
By the way, the Build ID is Build id: 200304070109
the date of build for /usr/sbin/qconn is 12th Aug 2003 - I believe it's the
installation date.
The size of qconn on my target is 70708 Bytes.
The file attached contains the content of my .log file after having tried to
debug my application.

Meanwhile I think it would be the best to reinstall Momentics version 6.2.0,
where this problem did not exist :-(

regards
Rüdiger Loos


"Alex Chapiro" <achapiro@qnx.com> schrieb im Newsbeitrag
news:bhak3c$r98$1@inn.qnx.com...
At least let me know Build ID from the About QNX Momentics IDE dialog.
For target please check the date of build for /usr/sbin/qconn.

"Rüdiger Loos" <Ruediger.Loos@3SOFT.de> wrote in message
news:bha8mq$je7$1@inn.qnx.com...
We definitely have version 6.2.1a installed on out host.
As I've heard from our customer, his/our target uses version 6.2.1, but
we
don't know whether it is 6.2.1 or 6.2.1a.
When I have the target connected to my host, how can I determine the
version
of the os installed on my target?

Thanks in advance
Rüdiger Loos

"Alex Chapiro" <achapiro@qnx.com> schrieb im Newsbeitrag
news:bh8ic0$ck9$1@inn.qnx.com...
Things keep getting to be more and more weird.:-))). I guess before
continuing of this issue investigation it is a good time to ask you
which
version are you using on your host and on your target? Host build
version
you can find in about dialog. As far as I remember, we never shipped
6.2.1A.
This is important to know in order to look at correct code.

Alex Chapiro


"Rüdiger Loos" <Ruediger.Loos@3SOFT.de> wrote in message
news:bh7mhp$mpr$1@inn.qnx.com...
I have no problem transfering the file from host to target using
file
system
navigator. Even larger files (10MB instead of 470kB) can be
transfered
without any problem.

"Alex Chapiro" <achapiro@qnx.com> schrieb im Newsbeitrag
news:bh0edt$g2t$1@inn.qnx.com...
According to your log report, exception occurs while transferring
file
from
host to target. Exception message is just an errno description.
Could
you
please try to copy the same file from host to /tmp on target,
using
File
System Navigator?

"Rüdiger Loos" <Ruediger.Loos@3SOFT.de> wrote in message
news:bh0cdg$el9$1@inn.qnx.com...
Hi Alex,

yes I've linked /tmp to /dev/shmem. But the space used does not
exceed
128kB.

Rüdiger

"Alex Chapiro" <achapiro@qnx.com> schrieb im Newsbeitrag
news:bh0bkt$e1p$1@inn.qnx.com...
Do you have /tmp linked to /dev/shmem? If so, how much space
it
uses
currently? It can easily exhaust your target memory.

Alex Chapiro

"Rüdiger Loos" <Ruediger.Loos@3SOFT.de> wrote in message
news:bgvo77$9m$1@inn.qnx.com...
No Mikhail, it does not.
This happens with every single application trying to debug.
I have 128MB RAM on my target and I can't debug a "hello
world"
program
:-(

Rüdiger

"Mikhail Khodjaiants" <mikhailk@qnx.com> schrieb im
Newsbeitrag
news:bgtqdo$je3$1@nntp.qnx.com...
It seems that your target is running out of memory.

Mikhail

"Rüdiger Loos" <Ruediger.Loos@3SOFT.de> wrote in message
news:bgt56j$3o5$1@inn.qnx.com...
Hallo David,

I think the important entries are:

--------------------------
!ENTRY org.eclipse.debug.ui 4 120 Jun 17, 2003
12:47:13.220
!MESSAGE Error logged from Debug UI:
!STACK 1
org.eclipse.core.runtime.CoreException[503]:
java.io.IOException:
Open
Not
enough memory
at










com.qnx.tools.utils.target.TargetServiceFile.connect(TargetServiceFile.java:
347)
at










com.qnx.tools.utils.target.TargetServiceFile.creat(TargetServiceFile.java:24
3)
at










com.qnx.tools.utils.target.TargetFileDownload.download(TargetFileDownload.ja
va:54)
at










com.qnx.tools.ide.qde.internal.ui.launch.LaunchConfigurationDelegate.perform
FileTransfer(LaunchConfigurationDelegate.java:443)
at










com.qnx.tools.ide.qde.internal.ui.launch.LaunchConfigurationDelegate.launch(
LaunchConfigurationDelegate.java:144)
at










org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigurati
on.java:136)
at










org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationDialog
$10.run(LaunchConfigurationDialog.java:2299)
at










org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext
.java:98)
!ENTRY com.qnx.tools.ide.qde.ui 4 503 Jun 17, 2003
12:47:13.220
!MESSAGE Can't transfer file for etx : Open Not enough
memory
!STACK 0
java.io.IOException: Open Not enough memory
at










com.qnx.tools.utils.target.TargetServiceFile.connect(TargetServiceFile.java:
347)
at










com.qnx.tools.utils.target.TargetServiceFile.creat(TargetServiceFile.java:24
3)
at










com.qnx.tools.utils.target.TargetFileDownload.download(TargetFileDownload.ja
va:54)
at










com.qnx.tools.ide.qde.internal.ui.launch.LaunchConfigurationDelegate.perform
FileTransfer(LaunchConfigurationDelegate.java:443)
at










com.qnx.tools.ide.qde.internal.ui.launch.LaunchConfigurationDelegate.launch(
LaunchConfigurationDelegate.java:144)
at










org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigurati
on.java:136)
at










org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationDialog
$10.run(LaunchConfigurationDialog.java:2299)
at










org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext
.java:98)
-------

and

-------
!ENTRY org.eclipse.debug.ui 4 120 Apr 07, 2003
15:13:49.875
!MESSAGE Error logged from Debug UI:
!STACK 1
org.eclipse.core.runtime.CoreException[150]:
java.io.IOException:
Exec
error:Launching failed
at
org.eclipse.cdt.utils.spawner.Spawner.exec(Spawner.java:215)
at
org.eclipse.cdt.utils.spawner.Spawner.<init>(Spawner.java:48)
at





org.eclipse.cdt.utils.spawner.ProcessFactory.exec(ProcessFactory.java:70)
at










org.eclipse.cdt.launch.internal.LocalCLaunchConfigurationDelegate.exec(Local
CLaunchConfigurationDelegate.java:213)
at










org.eclipse.cdt.launch.internal.LocalCLaunchConfigurationDelegate.launch(Loc
alCLaunchConfigurationDelegate.java:138)
at










org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfigurati
on.java:136)
at










org.eclipse.debug.internal.ui.actions.RelaunchActionDelegate.relaunch(Relaun
chActionDelegate.java:56)
at










org.eclipse.debug.internal.ui.actions.RelaunchActionDelegate.relaunch(Relaun
chActionDelegate.java:32)
at










org.eclipse.debug.internal.ui.actions.RelaunchHistoryLaunchAction$1.run(Rela
unchHistoryLaunchAction.java:59)
at


org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:66)
at










org.eclipse.debug.internal.ui.actions.RelaunchHistoryLaunchAction.run(Relaun
chHistoryLaunchAction.java:57)
at
org.eclipse.jface.action.Action.runWithEvent(Action.java:749)
at










org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(Action
ContributionItem.java:407)
at










org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent(ActionCont
ributionItem.java:361)
at










org.eclipse.jface.action.ActionContributionItem.access$0(ActionContributionI
tem.java:352)
at










org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent(A
ctionContributionItem.java:47)
at
org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:77)
at
org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:827)
at

org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:1529)
at

org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1291)
at

org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1343)
at
org.eclipse.ui.internal.Workbench.run(Workbench.java:1326)
at










org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.jav
a:831)
at
org.eclipse.core.boot.BootLoader.run(BootLoader.java:462)
at java.lang.reflect.Method.invoke(Native Method)
at
org.eclipse.core.launcher.Main.basicRun(Main.java:247)
at org.eclipse.core.launcher.Main.run(Main.java:703)
at org.eclipse.core.launcher.Main.main(Main.java:539)
-----

My momentics is running on a Windows XP PC an connected
via
Ethernet
with
my
X86 target.

The type of project is a "QNX C Application Project".

Regards

Rüdiger

P.S. I've heard of a patchB for Momentics 6.2.1 that
should
solve
the
problem?!?


"David Gibbs" <dagibbs@qnx.com> schrieb im Newsbeitrag
news:bgrblu$j0n$2@nntp.qnx.com...
"Ruediger Loos" <Ruediger.Loos@3soft.de> wrote:
Hallo,

I have a big problem in debugging my QNX
application.
I build my apps without any error and warning.
But when I start to debug my apps, I get a "Launch
Configuration
Error"
with
one of the following informations:
"Exception occured processing launch configuration.
Reason:
Failed
Launching
CDI Debugger: Error initializing: Exec
error:Launching
failed"
or
"Exception occured : Not enough memory"

Can anybody help me.

There's probably a .log file generated in
workspace/.metadata,
can
you
post the corresponding entry?

Also, what host are you running on?

Are you out of/low on system memory?

What type of project is it? (QNX C/C++? Standard
Make?)

-David
--
QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further
questions.



















begin 666 save.log
M(5-%4U-)3TX@075G(#$R+" R,# S(#$S.C$V.C0Q+C<T-2 M+2TM+2TM+2TM
M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2T-"FIA=F$N=F5R
M<VEO;CTQ+C,N,5\P- T*:F%V82YV96YD;W(]4W5N($UI8W)O<WES=&5M<R!)
M;F,N#0I";V]T3&]A9&5R(&-O;G-T86YT<SH@3U,]=VEN,S(L($%20T@]>#@V
M+"!74SUW:6XS,BP@3DP]9&5?1$4-"D-O;6UA;F0M;&EN92!A<F=U;65N=',Z
M("UO<R!W:6XS,B M=W,@=VEN,S(@+6%R8V@@>#@V("UF96%T=7)E(&-O;2YQ
M;G@N=&]O;',N:61E("UI;G-T86QL(&9I;&4Z0SHO44Y8<V1K+VAO<W0O=VEN
M,S(O>#@V+W5S<B]Q9&4O96-L:7!S92\-"B%%3E1262!O<F<N96-L:7!S92YJ
M9'0N;&%U;F-H:6YG(#0@-"!!=6<@,3(L(#(P,#,@,3,Z,38Z-#$N-S0U#0HA
M34534T%'12!632!T>7!E(&5L96UE;G0@=VET:"!U;FMN;W=N(&ED#0HA14Y4
M4ED@;W)G+F5C;&EP<V4N9&5B=6<N=6D@-" Q,C @075G(#$R+" R,# S(#$S
M.C$W.C U+C<R- T*(4U%4U-!1T4@17)R;W(@;&]G9V5D(&9R;VT@1&5B=6<@
M54DZ( T*(5-404-+(#$-"F]R9RYE8VQI<'-E+F-O<F4N<G5N=&EM92Y#;W)E
M17AC97!T:6]N6S$U,%TZ(&]R9RYE8VQI<'-E+F-D="YD96)U9RYC;W)E+F-D
M:2Y#1$E%>&-E<'1I;VXZ($5R<F]R(&EN:71I86QI>FEN9SH@5&EM961O=70-
M"@EA="!C;VTN<6YX+G1O;VQS+FED92YQ9&4N9&5B=6<N:6YT97)N86PN8V]R
M92Y#1T1"1&5B=6=G97(N8W)E871E071T86-H4V5S<VEO;BA#1T1"1&5B=6=G
M97(N:F%V83HQ,3@I#0H)870@8V]M+G%N>"YT;V]L<RYI9&4N<61E+FEN=&5R
M;F%L+G5I+FQA=6YC:"Y,875N8VA#;VYF:6=U<F%T:6]N1&5L96=A=&4N<W1A
M<G1$96)U9V=E<BA,875N8VA#;VYF:6=U<F%T:6]N1&5L96=A=&4N:F%V83HT
M,3,I#0H)870@8V]M+G%N>"YT;V]L<RYI9&4N<61E+FEN=&5R;F%L+G5I+FQA
M=6YC:"Y,875N8VA#;VYF:6=U<F%T:6]N1&5L96=A=&4N;&%U;F-H*$QA=6YC
M:$-O;F9I9W5R871I;VY$96QE9V%T92YJ879A.C,P-RD-"@EA="!O<F<N96-L
M:7!S92YD96)U9RYI;G1E<FYA;"YC;W)E+DQA=6YC:$-O;F9I9W5R871I;VXN
M;&%U;F-H*$QA=6YC:$-O;F9I9W5R871I;VXN:F%V83HQ,S8I#0H)870@;W)G
M+F5C;&EP<V4N9&5B=6<N:6YT97)N86PN=6DN;&%U;F-H0V]N9FEG=7)A=&EO
M;G,N3&%U;F-H0V]N9FEG=7)A=&EO;D1I86QO9R0Q,"YR=6XH3&%U;F-H0V]N
M9FEG=7)A=&EO;D1I86QO9RYJ879A.C(R.3DI#0H)870@;W)G+F5C;&EP<V4N
M:F9A8V4N;W!E<F%T:6]N+DUO9&%L0V]N=&5X="1-;V1A;$-O;G1E>'14:')E
M860N<G5N*$UO9&%L0V]N=&5X="YJ879A.CDX*0T*(45.5%)9(&]R9RYE8VQI
M<'-E+F-D="YL875N8V@@-" Q-3 @075G(#$R+" R,# S(#$S.C$W.C U+C<R
M- T*(4U%4U-!1T4@0T1)($5R<F]R.B!%<G)O<B!I;FET:6%L:7II;F<Z(%1I
M;65D;W5T#0HA4U1!0TL@, T*;W)G+F5C;&EP<V4N8V1T+F1E8G5G+F-O<F4N
M8V1I+D-$245X8V5P=&EO;CH@17)R;W(@:6YI=&EA;&EZ:6YG.B!4:6UE9&]U
M= T*"6%T(&-O;2YQ;G@N=&]O;',N:61E+G%D92YD96)U9RYI;G1E<FYA;"YC
M;W)E+D-'1$)$96)U9V=E<BYC<F5A=&5!='1A8VA397-S:6]N*$-'1$)$96)U
M9V=E<BYJ879A.C$Q."D-"@EA="!C;VTN<6YX+G1O;VQS+FED92YQ9&4N:6YT
M97)N86PN=6DN;&%U;F-H+DQA=6YC:$-O;F9I9W5R871I;VY$96QE9V%T92YS
M=&%R=$1E8G5G9V5R*$QA=6YC:$-O;F9I9W5R871I;VY$96QE9V%T92YJ879A
M.C0Q,RD-"@EA="!C;VTN<6YX+G1O;VQS+FED92YQ9&4N:6YT97)N86PN=6DN
M;&%U;F-H+DQA=6YC:$-O;F9I9W5R871I;VY$96QE9V%T92YL875N8V@H3&%U
M;F-H0V]N9FEG=7)A=&EO;D1E;&5G871E+FIA=F$Z,S W*0T*"6%T(&]R9RYE
M8VQI<'-E+F1E8G5G+FEN=&5R;F%L+F-O<F4N3&%U;F-H0V]N9FEG=7)A=&EO
M;BYL875N8V@H3&%U;F-H0V]N9FEG=7)A=&EO;BYJ879A.C$S-BD-"@EA="!O
M<F<N96-L:7!S92YD96)U9RYI;G1E<FYA;"YU:2YL875N8VA#;VYF:6=U<F%T
M:6]N<RY,875N8VA#;VYF:6=U<F%T:6]N1&EA;&]G)#$P+G)U;BA,875N8VA#
M;VYF:6=U<F%T:6]N1&EA;&]G+FIA=F$Z,C(Y.2D-"@EA="!O<F<N96-L:7!S
M92YJ9F%C92YO<&5R871I;VXN36]D86Q#;VYT97AT)$UO9&%L0V]N=&5X=%1H
M<F5A9"YR=6XH36]D86Q#;VYT97AT+FIA=F$Z.3@I#0HA4T534TE/3B!!=6<@
M,3(L(#(P,#,@,3,Z,C,Z,C,N,S@Q("TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM
M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+0T*:F%V82YV97)S:6]N/3$N,RXQ7S T
M#0IJ879A+G9E;F1O<CU3=6X@36EC<F]S>7-T96US($EN8RX-"D)O;W1,;V%D
M97(@8V]N<W1A;G1S.B!/4SUW:6XS,BP@05)#2#UX.#8L(%=3/7=I;C,R+"!.
M3#UD95]$10T*0V]M;6%N9"UL:6YE(&%R9W5M96YT<SH@+6]S('=I;C,R("UW
M<R!W:6XS,B M87)C:"!X.#8@+69E871U<F4@8V]M+G%N>"YT;V]L<RYI9&4@
M+6EN<W1A;&P@9FEL93I#.B]13EAS9&LO:&]S="]W:6XS,B]X.#8O=7-R+W%D
M92]E8VQI<'-E+PT*(45.5%)9(&]R9RYE8VQI<'-E+FID="YL875N8VAI;F<@
M-" T($%U9R Q,BP@,C P,R Q,SHR,SHR,RXS.#$-"B%-15-304=%(%9-('1Y
M<&4@96QE;65N="!W:71H('5N:VYO=VX@:60-"B%%3E1262!O<F<N96-L:7!S
M92YU:2 T(#0@075G(#$R+" R,# S(#$S.C(S.C0Y+C4Q.0T*(4U%4U-!1T4@
M56YA8FQE('1O(')E<W1O<F4@961I=&]R("T@8W)E871E16QE;65N="!R971U
M<FYE9"!N=6QL(&9O<B!I;G!U="!E;&5M96YT(&9A8W1O<GDZ(&]R9RYE8VQI
M<'-E+G5I+G!A<G0N1FEL945D:71O<DEN<'5T1F%C=&]R>0T*(45.5%)9(&]R
M9RYE8VQI<'-E+G5I(#0@-"!!=6<@,3(L(#(P,#,@,3,Z,C,Z-#DN-3,U#0HA
M34534T%'12!5;F%B;&4@=&\@<F5S=&]R92!E9&ET;W(@+2!C<F5A=&5%;&5M
M96YT(')E='5R;F5D(&YU;&P@9F]R(&EN<'5T(&5L96UE;G0@9F%C=&]R>3H@
M;W)G+F5C;&EP<V4N=6DN<&%R="Y&:6QE161I=&]R26YP=71&86-T;W)Y#0HA
M14Y44ED@;W)G+F5C;&EP<V4N=6D@-" T($%U9R Q,BP@,C P,R Q,SHR,SHT
M.2XU-3 -"B%-15-304=%(%5N86)L92!T;R!R97-T;W)E(&5D:71O<B M(&-R
M96%T945L96UE;G0@<F5T=7)N960@;G5L;"!F;W(@:6YP=70@96QE;65N="!F
M86-T;W)Y.B!O<F<N96-L:7!S92YU:2YP87)T+D9I;&5%9&ET;W));G!U=$9A
M8W1O<GD-"B%%3E1262!O<F<N96-L:7!S92YU:2 T(#0@075G(#$R+" R,# S
M(#$S.C(S.C0Y+C4U, T*(4U%4U-!1T4@56YA8FQE('1O(')E<W1O<F4@961I
M=&]R("T@8W)E871E16QE;65N="!R971U<FYE9"!N=6QL(&9O<B!I;G!U="!E
M;&5M96YT(&9A8W1O<GDZ(&]R9RYE8VQI<'-E+G5I+G!A<G0N1FEL945D:71O
M<DEN<'5T1F%C=&]R>0T*(45.5%)9(&]R9RYE8VQI<'-E+G5I(#0@-"!!=6<@
M,3(L(#(P,#,@,3,Z,C,Z-#DN-38V#0HA34534T%'12!5;F%B;&4@=&\@<F5S
M=&]R92!E9&ET;W(@+2!C<F5A=&5%;&5M96YT(')E='5R;F5D(&YU;&P@9F]R
M(&EN<'5T(&5L96UE;G0@9F%C=&]R>3H@;W)G+F5C;&EP<V4N=6DN<&%R="Y&
M:6QE161I=&]R26YP=71&86-T;W)Y#0HA14Y44ED@;W)G+F5C;&EP<V4N=6D@
M-" T($%U9R Q,BP@,C P,R Q,SHR,SHT.2XU-C8-"B%-15-304=%(%5N86)L
M92!T;R!R97-T;W)E(&5D:71O<B M(&-R96%T945L96UE;G0@<F5T=7)N960@
M;G5L;"!F;W(@:6YP=70@96QE;65N="!F86-T;W)Y.B!O<F<N96-L:7!S92YU
M:2YP87)T+D9I;&5%9&ET;W));G!U=$9A8W1O<GD-"B%%3E1262!O<F<N96-L
M:7!S92YC;W)E+G)E<V]U<F-E<R T(#$@075G(#$R+" R,# S(#$S.C,S.C V
M+C,Q,0T*(4U%4U-!1T4@4')O:F5C="!M:7-S:6YG(&EN('-E=$)U:6QD97)S
M4&5R<VES=&5N=$EN9F\-"B%%3E1262!O<F<N96-L:7!S92YC9'0N8V]R92 T
M(#(@075G(#$R+" R,# S(#$S.C,T.C$P+C<Y-PT*(4U%4U-!1T4@0T144')O
M:F5C="!A;')E861Y(&5X:7-I=',@8G5T(&1O97,@;F]T(&UA=&-H(&]W;F5R
M($E$(&]F(&-R96%T;W(-"B%%3E1262!O<F<N96-L:7!S92YU:2 T(# @075G
M(#$R+" R,# S(#$S.C,U.C4Y+C8V, T*(4U%4U-!1T4@06)S=')A8W1-87)K
M97)!;FYO=&%T:6]N36]D96PN8V]N;F5C=&5D#0HA14Y44ED@;W)G+F5C;&EP
M<V4N8V]R92YR97-O=7)C97,@-" S-C@@075G(#$R+" R,# S(#$S.C,U.C4Y
M+C8V, T*(4U%4U-!1T4@4F5S;W5R8V4@+W1E<W1#04XO8V]M;6]N+FUK(&1O
M97,@;F]T(&5X:7-T+@T*(45.5%)9(&]R9RYE8VQI<'-E+G5I(#0@-"!!=6<@
M,3(L(#(P,#,@,34Z,3@Z,S N-#@S#0HA34534T%'12!5;FAA;F1L960@97AC
M97!T:6]N(&-A=6=H="!I;B!E=F5N="!L;V]P+@T*(45.5%)9(&]R9RYE8VQI
M<'-E+G5I(#0@,"!!=6<@,3(L(#(P,#,@,34Z,3@Z,S N-3$T#0HA34534T%'
M12!J879A+FQA;F<N3G5L;%!O:6YT97)%>&-E<'1I;VX-"B%35$%#2R P#0IJ
M879A+FQA;F<N3G5L;%!O:6YT97)%>&-E<'1I;VX-"@EA="!O<F<N96-L:7!S
M92YJ9F%C92YA8W1I;VXN06-T:6]N0V]N=')I8G5T:6]N271E;2X\:6YI=#XH
M06-T:6]N0V]N=')I8G5T:6]N271E;2YJ879A.C$S,RD-"@EA="!O<F<N96-L
M:7!S92YJ9F%C92YA8W1I;VXN0V]N=')I8G5T:6]N36%N86=E<BYA9&0H0V]N
M=')I8G5T:6]N36%N86=E<BYJ879A.C8R*0T*"6%T(&-O;2YQ;G@N=&]O;',N
M:61E+F9S>7,N=6DN1FEL95-Y<W1E;59I97<N9FEL;%1R965#;VYT97AT365N
M=2A&:6QE4WES=&5M5FEE=RYJ879A.C0R-2D-"@EA="!C;VTN<6YX+G1O;VQS
M+FED92YF<WES+G5I+D9I;&53>7-T96U6:65W)#$N;65N=4%B;W5T5&]3:&]W
M*$9I;&53>7-T96U6:65W+FIA=F$Z,C@P*0T*"6%T(&]R9RYE8VQI<'-E+FIF
M86-E+F%C=&EO;BY-96YU36%N86=E<BYF:7)E06)O=714;U-H;W<H365N=4UA
M;F%G97(N:F%V83HR,S4I#0H)870@;W)G+F5C;&EP<V4N:F9A8V4N86-T:6]N
M+DUE;G5-86YA9V5R+FAA;F1L94%B;W5T5&]3:&]W*$UE;G5-86YA9V5R+FIA
M=F$Z,S V*0T*"6%T(&]R9RYE8VQI<'-E+FIF86-E+F%C=&EO;BY-96YU36%N
M86=E<BYA8V-E<W,D,"A-96YU36%N86=E<BYJ879A.C,P,RD-"@EA="!O<F<N
M96-L:7!S92YJ9F%C92YA8W1I;VXN365N=4UA;F%G97(D,BYM96YU4VAO=VXH
M365N=4UA;F%G97(N:F%V83HS,S,I#0H)870@;W)G+F5C;&EP<V4N<W=T+G=I
M9&=E=',N5'EP961,:7-T96YE<BYH86YD;&5%=F5N="A4>7!E9$QI<W1E;F5R
M+FIA=F$Z,3$T*0T*"6%T(&]R9RYE8VQI<'-E+G-W="YW:61G971S+D5V96YT
M5&%B;&4N<V5N9$5V96YT*$5V96YT5&%B;&4N:F%V83HW-RD-"@EA="!O<F<N
M96-L:7!S92YS=W0N=VED9V5T<RY7:61G970N<V5N9$5V96YT*%=I9&=E="YJ
M879A.C@T,RD-"@EA="!O<F<N96-L:7!S92YS=W0N=VED9V5T<RY7:61G970N
M<V5N9$5V96YT*%=I9&=E="YJ879A.C@T."D-"@EA="!O<F<N96-L:7!S92YS
M=W0N=VED9V5T<RY#;VYT<F]L+E=-7TE.251-14Y54$]055 H0V]N=')O;"YJ
M879A.C,P,C@I#0H)870@;W)G+F5C;&EP<V4N<W=T+G=I9&=E=',N0V]N=')O
M;"YW:6YD;W=0<F]C*$-O;G1R;VPN:F%V83HR-S Q*0T*"6%T(&]R9RYE8VQI
M<'-E+G-W="YW:61G971S+D1E8V]R871I;VYS+G=I;F1O=U!R;V,H1&5C;W)A
M=&EO;G,N:F%V83HQ,S0P*0T*"6%T(&]R9RYE8VQI<'-E+G-W="YW:61G971S
M+D1I<W!L87DN=VEN9&]W4')O8RA$:7-P;&%Y+FIA=F$Z,3DY,BD-"@EA="!O
M<F<N96-L:7!S92YS=W0N:6YT97)N86PN=VEN,S(N3U,N5')A8VM0;W!U<$UE
M;G4H3F%T:79E($UE=&AO9"D-"@EA="!O<F<N96-L:7!S92YS=W0N=VED9V5T
M<RY-96YU+G-E=%9I<VEB;&4H365N=2YJ879A.CDP,RD-"@EA="!O<F<N96-L
M:7!S92YS=W0N=VED9V5T<RY#;VYT<F]L+E=-7T-/3E1%6%1-14Y5*$-O;G1R
M;VPN:F%V83HR.#,Y*0T*"6%T(&]R9RYE8VQI<'-E+G-W="YW:61G971S+D-O
M;G1R;VPN=VEN9&]W4')O8RA#;VYT<F]L+FIA=F$Z,C8X,RD-"@EA="!O<F<N
M96-L:7!S92YS=W0N=VED9V5T<RY$:7-P;&%Y+G=I;F1O=U!R;V,H1&ES<&QA
M>2YJ879A.C$Y.3(I#0H)870@;W)G+F5C;&EP<V4N<W=T+FEN=&5R;F%L+G=I
M;C,R+D]3+D-A;&Q7:6YD;W=0<F]C5RA.871I=F4@365T:&]D*0T*"6%T(&]R
M9RYE8VQI<'-E+G-W="YI;G1E<FYA;"YW:6XS,BY/4RY#86QL5VEN9&]W4')O
M8RA/4RYJ879A.C$Q-38I#0H)870@;W)G+F5C;&EP<V4N<W=T+G=I9&=E=',N
M5')E92YC86QL5VEN9&]W4')O8RA4<F5E+FIA=F$Z,34R*0T*"6%T(&]R9RYE
M8VQI<'-E+G-W="YW:61G971S+D-O;G1R;VPN5TU?4D)55%1/3E50*$-O;G1R
M;VPN:F%V83HS-S4Q*0T*"6%T(&]R9RYE8VQI<'-E+G-W="YW:61G971S+D-O
M;G1R;VPN=VEN9&]W4')O8RA#;VYT<F]L+FIA=F$Z,C<S-2D-"@EA="!O<F<N
M96-L:7!S92YS=W0N=VED9V5T<RY$:7-P;&%Y+G=I;F1O=U!R;V,H1&ES<&QA
M>2YJ879A.C$Y.3(I#0H)870@;W)G+F5C;&EP<V4N<W=T+FEN=&5R;F%L+G=I
M;C,R+D]3+D1I<W!A=&-H365S<V%G95<H3F%T:79E($UE=&AO9"D-"@EA="!O
M<F<N96-L:7!S92YS=W0N:6YT97)N86PN=VEN,S(N3U,N1&ES<&%T8VA-97-S
M86=E*$]3+FIA=F$Z,3(R,RD-"@EA="!O<F<N96-L:7!S92YS=W0N=VED9V5T
M<RY$:7-P;&%Y+G)E861!;F1$:7-P871C:"A$:7-P;&%Y+FIA=F$Z,3(X.2D-
M"@EA="!O<F<N96-L:7!S92YU:2YI;G1E<FYA;"Y7;W)K8F5N8V@N<G5N179E
M;G1,;V]P*%=O<FMB96YC:"YJ879A.C$S-#,I#0H)870@;W)G+F5C;&EP<V4N
M=6DN:6YT97)N86PN5V]R:V)E;F-H+G)U;BA7;W)K8F5N8V@N:F%V83HQ,S(V
M*0T*"6%T(&]R9RYE8VQI<'-E+F-O<F4N:6YT97)N86PN8F]O="Y);G1E<FYA
M;$)O;W1,;V%D97(N<G5N*$EN=&5R;F%L0F]O=$QO861E<BYJ879A.C@S,2D-
M"@EA="!O<F<N96-L:7!S92YC;W)E+F)O;W0N0F]O=$QO861E<BYR=6XH0F]O
M=$QO861E<BYJ879A.C0V,BD-"@EA="!J879A+FQA;F<N<F5F;&5C="Y-971H
M;V0N:6YV;VME*$YA=&EV92!-971H;V0I#0H)870@;W)G+F5C;&EP<V4N8V]R
M92YL875N8VAE<BY-86EN+F)A<VEC4G5N*$UA:6XN:F%V83HR-#<I#0H)870@
M;W)G+F5C;&EP<V4N8V]R92YL875N8VAE<BY-86EN+G)U;BA-86EN+FIA=F$Z
M-S S*0T*"6%T(&]R9RYE8VQI<'-E+F-O<F4N;&%U;F-H97(N36%I;BYM86EN
1*$UA:6XN:F%V83HU,SDI#0H`
`
end

Post Reply

Return to “qdn.public.devtools”