-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
freebsd core dump #2
Comments
This happens because Elymas does not depend on libc, but instead does everything itself. It happily expects the Linux syscall interface. To port Elymas to BSD, all syscall invocations must be ported. Look here for example: |
ok I'll check it out and let u know if I make it |
Wouldn't it be considerably more practical to just link with a libc, even if it's just a small portable one like newlib? Especially in terms of porting, but also compatbility. |
Define "practical". Linking against shared libraries would mean to replace / patch the memory allocation routine when waking up from the first freeze (before freeze we'd have to use the Perl-loaded mmap, after freeze whatever the linker came up with.) I'll put it into the TODO for the time being... |
freebsd amd64 has same syscall call convention. Only call numbers and constants number are differents. I changed some syscall numbers in compiler/standardClient.ey and compiler/elymasAsmLib.ey The core dump does not occurs now but still some error occurs : |
I think, it's probably best if I take a look at this on a FreeBSD system. Need to grab one first though, this might take a while. |
no problem. |
I'd be glad to hear whether you have any success with the new freebsd branch (I'll put it into some arch directory later, but let's first see what really needs to be changed...) Shared library support is not there yet, so you'll only get the |
Shared library support is now available. You might get a |
Nice! Once you've got the FreeBSD thing merged into the main branch in some arch folder or something, I might port Elymas to Xelix just for the heck of it. 😸 |
hello, |
FYI: FreeBSD support is now in master, please switch away from the freebsd branch (which I pruned). |
Seems like it fails on ubuntu, probably the same problem as before |
@shadowys Sorry for late answer, was away during easter. Thanks for trying to build and reporting a failure. Could you be more specific about what you observed while trying to build (ideally a log or screencast) and which Ubuntu Version you use exactly? I'm rather certain, it's not the same problem I had on FreeBSD (wrong syscall numbers), because Ubuntu does use a Linux kernel and thus the same syscall numbers my Debian has. |
Hmm, it might be something else then, this is what I did: https://asciinema.org/a/bgt2p6zit6vvfvhxb14p0l4ao
I tried it on CloudLinux and it works perfectly fine. |
Now that is sure interesting, thank you very much indeed. I'll have a look with some Ubuntu VM, but it might take some days (busy with work). |
hi,
I could not compile Elymas.
OS:
$ uname -a
FreeBSD darkstar 10.1-STABLE FreeBSD 10.1-STABLE #0 r277559: Fri Jan 23 10:05:15 CET 2015 root@darkstar:/usr/obj/usr/src/sys/THINKPKERNEL amd64
PERL version:
$ perl -v
This is perl 5, version 14, subversion 4 (v5.14.4) built for amd64-freebsd
it stop here :
$ gmake
......
cd compiler &&
../interpreter/elymas elymas.ey ../elymas/interpreter.ey
Makefile:7: recipe for target 'elymas/interpreter' failed
gmake: *** [elymas/interpreter] Segmentation fault (core dumped)
The text was updated successfully, but these errors were encountered: