World: r3wp

should be a quick way to test this particular problem, yes

ah, crap, no

empty compiles, at least

yeah, but it generates crap :)

Andreas, shouldn't it be rather:
data-ptr: code-ptr + code-size + (page-size // code-size)

yeah, if we want to do proper alignment :)

but it results in the same problem of generating wrong file offsets

(because other code parts re-use data-ptr to calculate the file offset)

give me a few minutes, i'll try to generate a binary that has that 
fixed

I don't think the GCC folks can do debug cycles this fast :-)

you can (it's only C, after all), but you need a quite beefy machine. 
LLVM (C++) on the other hand ...

soo, here we go

http://bolka.at/2011/tmp/hello

trying...

or if you want to compile the binaries on your own:
https://gist.github.com/1bf8d5c54cb630c83d8e

hmm, the browser don't want to save it to disk, it just displays 
it as text...I guess it misses a content-type: application/octet-stream...

Kaj: any workaround?

http://bolka.at/2011/tmp/hello.bin

Andreas: you rules!

Hello is working

nice :)

Displays all the banners, but seg fault on exiting.

anything in the kernel log?

uploading a screenshot...

http://static.red-lang.org/tmp/syllable-hello.png

The error is: 
Error: sys_open() failed to dup path

Invalid pagefault at 000000ec (NOTP:WRITE:USER)

Got to go, will be back in an hour.

I think right-clicking in the browser would work

My NginX configuration probably serves it as default text

One of the syscalls has a different number on Syllable, probably 
exit. I'll check

The screenshot is awesome :-)

exit is syscall 5 instead of syscall 1 on Linux

I've taken over Andreas' changes, corrected the runtime syscall, 
and uploaded new empty, hello, reply-server and request-client

The latter won't find the 0MQ library, but will show how that works 
on Syllable

My nginx.conf has default_type application/octet-stream; by the way

could you paste a `readelf -a` of some small system binary somewhere?

Will do

New hello still segfaults.

Program counter address: EIP = 1234567a

EAX = 000000ec (seems that dereferencing EAX is what caused the error)

I was afraid syscalls would be more problematic. What calling convention 
do you use for them?

Let me see that...

1st argument => EBX
2nd argument => ECX
3rd argument => EDX
...
syscall ID => EAX
INT 0x80

What is that called?

Linux is using SYSENTER/SYSCALL, but Syllable still uses int 0x80:

http://development.syllable.org/news/2009-05-24-16-19-Memory-mapped-input-output-implemented.html

I can't find the source document anymore, I remember that it was 
the standard Linux way (pre-SYSENTER).

I thought so, considering that Hello works to my surprise :-)

Is there a native code debugger on Syllable/Desktop?