I’m sorry, but the version you tested was barely later than early release of
Patch A candidate (tagget 11/03/03). I can see it from the supplemented
trace log. It doesn’t make sence to play with it. Could you please do the
same using Patch B installation?
Alex
“Rüdiger Loos” <Ruediger.Loos@3SOFT.de> wrote in message
news:bhd4tk$n9m$1@inn.qnx.com…
Ok, now I performed the following steps:
- I deleted all debug targets
- I closed the IDE
- I removed my .log file
- I started the IDE
- I tried to debug my app as a "local application
the result was the error message box in locApp.bmp and the log file
locApp.logThe I performed the following steps:
- I removed my .log file
- I started the IDE
- I created a new “launch configuration” QNX QConn (IP); the only change
I
did was to specify my target- I pressed the debug button
the result was the error message box in qconnApp.bmp and the log file
qconnApp.logThe problem is the second “tabletest_mb” directory.
The real path is “E:\Pro\MED_ETX1\code\tabletest_mb\x86\o-g”
and NOT “E:\Pro\MED_ETX1\code\tabletest_mb\tabletest_mb\x86\o-g”
but who made a mistake and how can I correct the mistake?
“Alex Chapiro” <> achapiro@qnx.com> > schrieb im Newsbeitrag
news:bhb66r$ajt$> 1@inn.qnx.com> …
I don’t think it is a good idea. This is the first case we run into this
problem.
Unfortunately the log you send me does not correspond the described
problem.
If you installed Patch B, please remove .log, start IDE, try operation
you
cannot perform, close IDE and send me .log together with snapshot of the
error message box. I helps to identify the problem.Thanks,
Alex
“Rüdiger Loos” <> Ruediger.Loos@3SOFT.de> > wrote in message
news:bhb0u0$750$> 1@inn.qnx.com> …
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.(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)
atorg.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)
atorg.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.
\