Project Home
Project Home
Trackers
Trackers
Documents
Documents
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - Cannot launch remote application: "error: not enough memory": (10 Items)
   
Cannot launch remote application: "error: not enough memory"  
Hello,

Have mercy, I am following the "10 steps to developing a QNX program" tutorial.

I have created a c application in Momentics and have attached to my target VMware-based system.

Whether I launch the debug configuration or the run configuration, I get the following error:
---
Title: 
Problem Occurred

Text:
'Downloading and starting the application ...' has encountered a problem.
Error starting remote application.

Details:
Error starting remote application.
Target launcher@<192.168.1.105:8000>: Error: Not enough memory
---

I am developing on Windows 7 using the Momentics IDE. I am capable of connecting to my target vmware system using the 
System Information view as in the 10 steps tutorial. 

I know that there is enough RAM free in the vmware image. I have tried both starting in /tmp and /usr/tmp, and am logged
 in as root on the vmware image.

Why is it saying there is not enough memory?

Thank you,
Chris
Re: Cannot launch remote application: "error: not enough memory"  
How do you know it is enough memory? What system information reports - how much memory left?

On 09/15/2011 11:19 AM, Chris Cameron wrote:
> Hello,
> 
> Have mercy, I am following the "10 steps to developing a QNX program" tutorial.
> 
> I have created a c application in Momentics and have attached to my target VMware-based system.
> 
> Whether I launch the debug configuration or the run configuration, I get the following error:
> ---
> Title: 
> Problem Occurred
> 
> Text:
> 'Downloading and starting the application ...' has encountered a problem.
> Error starting remote application.
> 
> Details:
> Error starting remote application.
> Target launcher@<192.168.1.105:8000>: Error: Not enough memory
> ---
> 
> I am developing on Windows 7 using the Momentics IDE. I am capable of connecting to my target vmware system using the 
System Information view as in the 10 steps tutorial. 
> 
> I know that there is enough RAM free in the vmware image. I have tried both starting in /tmp and /usr/tmp, and am 
logged in as root on the vmware image.
> 
> Why is it saying there is not enough memory?
> 
> Thank you,
> Chris
> 
> 
> 
> _______________________________________________
> 
> General
> http://community.qnx.com/sf/go/post88861
> 
Re: Cannot launch remote application: "error: not enough memory"  
System information panel says there is 193M free RAM of 256M RAM given by the vmware image.
RE: Cannot launch remote application: "error: not enough memory"  
You can try to run your app in the VM through a telnet session to see if it starts. The error you see from IDE signals 
the app can't be run on it.

Also are you running the x86 binary in the VM?

-----Original Message-----
From: Chris Cameron [mailto:community-noreply@qnx.com] 
Sent: September-15-11 11:19 AM
To: general-ide
Subject: Cannot launch remote application: "error: not enough memory"

Hello,

Have mercy, I am following the "10 steps to developing a QNX program" tutorial.

I have created a c application in Momentics and have attached to my target VMware-based system.

Whether I launch the debug configuration or the run configuration, I get the following error:
---
Title: 
Problem Occurred

Text:
'Downloading and starting the application ...' has encountered a problem.
Error starting remote application.

Details:
Error starting remote application.
Target launcher@<192.168.1.105:8000>: Error: Not enough memory
---

I am developing on Windows 7 using the Momentics IDE. I am capable of connecting to my target vmware system using the 
System Information view as in the 10 steps tutorial. 

I know that there is enough RAM free in the vmware image. I have tried both starting in /tmp and /usr/tmp, and am logged
 in as root on the vmware image.

Why is it saying there is not enough memory?

Thank you,
Chris

Re: RE: Cannot launch remote application: "error: not enough memory"  
I am running the x86 binary, since the vmware is "x86pc" target. Tried the release and debug (_g) versions.

Also, just noticed that the console outputs this, in addition to the other "popup" error I described before:

.gdbinit: No such file or directory.

I don't know if this is just a casualty of the upload failing, another error altogether, or the root cause.

I am not sure how I can use telnet here to help. I manually transferred the release binaries over to the target platform
 through the Momentics file browser. I get the same error there:

./sockets
/bin/sh: ./sockets: Not enough memory

Surely 192MB of ram is enough to run this.
RE: RE: Cannot launch remote application: "error: not enough memory"  
The waring on ".gdbinit" is not an error. It just means you haven't defined the init file.

You have confirmed your binary throws the same error when running in the target directly so this does look like error 
from your source code. Do you try to allocate a big chunk of memory in your app?

-----Original Message-----
From: Chris Cameron [mailto:community-noreply@qnx.com] 
Sent: September-15-11 12:33 PM
To: general-ide
Subject: Re: RE: Cannot launch remote application: "error: not enough memory"

I am running the x86 binary, since the vmware is "x86pc" target. Tried the release and debug (_g) versions.

Also, just noticed that the console outputs this, in addition to the other "popup" error I described before:

.gdbinit: No such file or directory.

I don't know if this is just a casualty of the upload failing, another error altogether, or the root cause.

I am not sure how I can use telnet here to help. I manually transferred the release binaries over to the target platform
 through the Momentics file browser. I get the same error there:

./sockets
/bin/sh: ./sockets: Not enough memory

Surely 192MB of ram is enough to run this.



_______________________________________________

General
http://community.qnx.com/sf/go/post88868
Re: RE: RE: Cannot launch remote application: "error: not enough memory"  
I had thought that originally, and had reduced two char arrays down to only 256K each. Literally the only thing I 
instantiate. Still got the error. So I reduced them further to 256 bytes each and now it's getting passed the "Not 
enough memory error".

Even at 256KB each that's only half a MB.

Is there some (very low) upper limit of in-process memory for x86-based neutrino?
Re: Cannot launch remote application: "error: not enough memory"  
Where do you define your arrays? Are they local (i.e. stack) variables?


On 11-09-15 12:53 PM, Chris Cameron wrote:
> I had thought that originally, and had reduced two char arrays down to only 256K each. Literally the only thing I 
instantiate. Still got the error. So I reduced them further to 256 bytes each and now it's getting passed the "Not 
enough memory error".
>
> Even at 256KB each that's only half a MB.
>
> Is there some (very low) upper limit of in-process memory for x86-based neutrino?
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post88870
>
Re: Cannot launch remote application: "error: not enough memory"  
Good call. I was initializing them on the stack at the top of the C file, i.e. 

char blah[256*1024] = {0};

So I changed them to char*'s and allocate them on the heap instead inside functions, as they are needed.

Still surprised the stack fills up somewhere between 256 and 512KB.

Thanks everyone.
Re: Cannot launch remote application: "error: not enough memory"  
On 11-09-16 12:05 AM, Chris Cameron wrote:
> Good call. I was initializing them on the stack at the top of the C file, i.e.
>
> char blah[256*1024] = {0};
>
> So I changed them to char*'s and allocate them on the heap instead inside functions, as they are needed.
>
> Still surprised the stack fills up somewhere between 256 and 512KB.

The initial thread's default stack size is 512KB on all platforms except 
ARM where it is 128KB. You can use ldrel -L -S <size> <executable> or 
qcc -N to specify a larger default stack size.

Regards,

Ryan Mansfield