Index
> Non-x86 architectures > FASMARM: out of memory... |
| Author |
|
|
LocoDelAssembly 20 Jan 2012, 21:58
Can you show the code? You could try the -m parameter to give fasmarm more memory, but 16 MB should really be enough if the code really doesn't have DUPs or any other thing that can increase the memory requirements considerably.
|
|||
20 Jan 2012, 21:58 |
|
|
Coty 20 Jan 2012, 22:04
Yeah
Code: ;=========================================================; ; Hello world example for Darwin 11 ARM. ;=========================================================; format ELF executable entry start segment readable executable start: mov r12, 4 ; r12 = write text ldr r1, [_hello] ; Our message mov r0, 1 ; stdout mov r2, length ; msg length swi 0x80 ; Just do it ;------------------------------; ; Syscall exit. ; ;------------------------------; mov r12, 1 ; Exit mov r0, 0 ; return status 0 swi 0x80 ; astalavista baby ;==========================================================; ; Data area. ; ;==========================================================; _hello rw msg msg: db "Hello Darwin world from assembly!",0 length = $ - msg segment writeable I also tried to allocate 128m and that failed (I though "if this don't do it, then nothing will!") Last edited by Coty on 20 Jan 2012, 22:13; edited 1 time in total |
|||
|
20 Jan 2012, 22:04 |
|
|
LocoDelAssembly 20 Jan 2012, 22:12
Code: _hello rw msg |
|||
|
20 Jan 2012, 22:12 |
|
|
Coty 20 Jan 2012, 22:15
DO'H! Interesting that would through an out of memory error though...
Thanks  |
|||
|
20 Jan 2012, 22:15 |
|
|
LocoDelAssembly 20 Jan 2012, 22:29
Well, your code will take as much memory as the msg address value is, so it is not that surprising (although it is interesting how a single character can impact so much in memory consumption
 ) |
|||
|
20 Jan 2012, 22:29 |
|
|
revolution 24 Jan 2012, 12:26
Also note that the old ARM11 chip does not support all the latest instruction set additions.
Always remember to set your "processor" and "coprocessor" values to avoid disappointment with code crashing when trying to execute unsupported instructions. |
|||
|
24 Jan 2012, 12:26 |
|
|
revolution 24 Jan 2012, 23:57
LocoDelAssembly wrote: Well, your code will take as much memory as the msg address value is ... |
|||
|
24 Jan 2012, 23:57 |
|
|
Coty 25 Jan 2012, 16:56
revolution wrote: Also note that the old ARM11 chip does not support all the latest instruction set additions. Oh yeah! I forgot about that, maybe that was my problem of why it wouldn't run, I'll have to try that when I get the chance... |
|||
|
25 Jan 2012, 16:56 |
|
|
Dex4u 25 Jan 2012, 20:08
Coty, is your device jailbreak and what device is it ?.
|
|||
|
25 Jan 2012, 20:08 |
|
|
Coty 15 Mar 2012, 20:02
Oh sorry, missed your reply somehow dex.
It is an ipod touch 4g, with iOS 5.0, yes it's jail broken. I have written this on how one may dev for it with linux: http://my.opera.com/coty0010/blog/2012/01/20/writing-an-app-for-ios-5-with-linux |
|||
|
15 Mar 2012, 20:02 |
|
|
Dex4u 16 Mar 2012, 00:44
Coty wrote: Oh sorry, missed your reply somehow dex. Cool thanks, i have one of those, i will give it a try. |
|||
|
16 Mar 2012, 00:44 |
|
|
Tonymac32 02 Jun 2012, 04:55
Revolution: I just ran into Coty's issue while browsing the forums, your post in the thread about loading large immediate values shows the "rw" instead of "dw" usage. Just thought I'd mention it before someone else stumbles over it. Thanks for all the support you're giving the community.
|
|||
|
02 Jun 2012, 04:55 |
|
|
revolution 02 Jun 2012, 04:58
Tonymac32 wrote: Revolution: I just ran into Coty's issue while browsing the forums, your post in the thread about loading large immediate values shows the "rw" instead of "dw" usage. Just thought I'd mention it before someone else stumbles over it. Thanks for all the support you're giving the community. |
|||
|
02 Jun 2012, 04:58 |
|
< Last Thread | Next Thread > |
Forum Rules:
|