Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 15 Dec 2017 13:33:31 +0100
From: Szabolcs Nagy <>
Subject: Re: [PATCH] split __libc_start_main.c into two files (Wasm)

* Nicholas Wilson <> [2017-12-15 11:34:10 +0000]:
> To clarify, it's not exit() itself that's a problem. Remember we're using statically-linked syscalls, so linking in exit() introduces a dependency on SYS_exit_group/SYS_exit, which Wasm pulls in as external dependencies in the host emulation environment. It would be nice to avoid linking in syscalls that aren't actually used, especially ones like SYS_exit that are a bit ugly to emulate.

why is exit ugly?
halting execution should not be complicated on whatever platform

how do you implement a_crash?
the c runtime uses that all over the place anyway so it's unlikely
that you can get away without process termination code.

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.