Stavros Aronis

http://erlang.org/doc/man/kernel_app.html#erl_signal_server

Or just turn the right parts of Concuerror into an application.

I am removing the milestone as I cannot find any easy way to do this for the time being and I'd rather have a version 1.0.0 than wait for it.

@kostis, I prefer to accept the PR sooner, rather than wait until 'everything is done'. I also disagree that it is 'really bad'. Moving the few lines of code makes...

Actually, I think that we can fix #299 by adding a `{binary, Binary}` option, usable from `concuerror:run([...])` that uses the newly exposed `load_binary/3` code.

This is not needed for 1.0.0

Hi @hauleth ! Interesting (and hard) case! Thank you for spending time to make an Erlang equivalent. Concuerror needs the abstract syntax tree of a module in order to instrument...

@hauleth Right, but I am afraid that this is a design decision: there are no such introspection capabilities (i.e. "show me the abstract code of this loaded beam for which...

@hauleth Such an API can be built by: - exporting a `load_binary/3` in https://github.com/parapluu/Concuerror/blob/master/src/concuerror_loader.erl (the value for the `Instrumented` argument is returned by `get_instrumented_table`) - invoking Concuerror by: ``` concuerror_loader:initialise([]),...

The `--after-timeout` applying to timers as well makes perfect sense. Thanks for pointing this out! Will be fixed (soon)!