Thank you.
I no longer see the APserver termination message upon an attention
signal.
However, the segfault and backtrace still happens when APL runs inside
Emacs.
Also, please note my other post regarding detection of the attention
signal.
On Mon, 2014-07-21 at 12:24 +0200, Juergen Sauermann wrote:
Hi David,
thanks, should be fixed in SVN 381.
/// Jürgen
On 07/20/2014 07:40 PM, David Lamkins wrote:
Jüergen and Elias, I think there might be something here for each of
you.
See comments in attached test case.
There are two transcripts following:
1. From within gnu-apl-mode:
)load foo
loading )DUMP file /home/dlamkins/APL/workspaces/foo.apl...
WAS CLEAR WS
test
test C-c C-c
=====
APserver terminated by SIGINT===================================
============
SEGMENTATION FAULT
----------------------------------------
-- Stack trace at main.cc:133
----------------------------------------
0x7fa1346e2d65 __libc_start_main
0x43af15 main
0x53344d Workspace::immediate_execution(bool)
0x473135 Command::process_line()
0x46d17a Command::do_APL_expression(UCS_string&)
0x47c955 Executable::execute_body() const
0x4ed880 StateIndicator::run()
0x4a34f0 Prefix::reduce_statements()
0x4fe799 Symbol::resolve(Token&, bool)
0x5095fd Quad_QUOTE::get_apl_value() const
0x487e4b Input::get_quad_cr_line(UCS_string)
0x7fa13474761a strlen
0x7fa1361a3750
0x48dada
========================================
====================================================
Process apl exited abnormally with code 3
2. When run standalone in a terminal:
)load foo
loading )DUMP file /home/dlamkins/APL/workspaces/foo.apl...
WAS CLEAR WS
test
test ^C
APserver terminated by SIGINT
^C
ATTENTION
test[2] →loop
^
--
"The secret to creativity is knowing how to hide your sources."
Albert Einstein
http://soundcloud.com/davidlamkins
http://reverbnation.com/lamkins
http://reverbnation.com/lcw
http://lamkins-guitar.com/
http://lamkins.net/
http://successful-lisp.com/