2017-08-24 13:40 GMT+02:00, Luís Oliveira luismbo@gmail.com:
Heh, that's quite bizarre. Keep us posted.
ok, here the next update:
I wasn't really correct with my previous description, so I will be more precise here:
- I start swank on android (the REPL uses ECL) - now I connect from the pc, which breaks into the Slime debugger, as expected (caused by 'break') - as soon as I click on any function of the "Backtrace:" list, the Slime REPL is shown with its usual prompt (here: "EQL-USER>")
The Slime REPL is fully functioning. Now if I provoke a condition, e.g. (/ 0), the debugger just adds 2 more restarts (as usual), and if I select the top most ABORT, the REPL keeps functioning.
Of course if I select to abort from 'break' (for the record: set by me at the start of swank::close-connection%), then I lose the connection to swank.
Attached you find the fully expanded backtrace. The only condition is from the inserted break (I clicked on all of the listed ones; it always says "Break" after FORMAT-CONTROL, (see top of attached file).
In function close-connection (from backtrace), the condition simply says NIL.
I really have no clue so far...
Luís
On Thu, Aug 24, 2017, 10:42 PR polos.ruetz@gmail.com wrote:
2017-08-23 23:36 GMT+02:00, Luís Oliveira luismbo@gmail.com:
you could try to place a break at the start of swank::close-connection% to see what's triggering it
Thank you very much, I'm closer now (although it doesn't work normally yet).
If I put a break at the start of swank::close-connection%, Emacs shows the debugger right after I connect to swank; then (and this is strange), after a few seconds, the REPL shows up in the other half of Emacs, and it works!!
So, I have now the debugger open, and a functioning REPL (until I continue from the break); but the open debugger doesn't stop the REPL from functioning, and on conditions on the REPL, another debugger instance will show, so I can fully use the REPL.
Now I'll need to examine the backtrace carefully...
Thanks again,
Paul
HTH, Luís