#242 Ctrl-C stops the computation of goals specified by the -e option instead of creating a break

[Ed Schwartz]

When XSB is processing a goal specified by the -e command line argument, pressing Ctrl-C stops the computation instead of creating a break. Pressing Ctrl-D at that point (or typing end_of_file.) does not resume the computation, but exits XSB. I expected the behavior of Ctrl-C to be the same as if I had typed the query at the prompt.

[Ed Schwartz]

I was testing this a little more, and I was wrong about the cause. It's not whether the goal is specified via -e. I'm unclear why sometimes I'm getting a break and sometimes the computation is being halted.

Here's an example where it works as expected:

^C[ Break (level 1) ]
1: ?- [ End break (level 1) ]

Here's an example where I press Ctrl-C and the computation stops:

C++Error[XSB/Runtime/P]: [Miscellaneous] Aborting...
Forward Continuation...
... machine:xsb_backtrace/1  From /home/eschwartz/pharos/build/src/XSB/XSB/syslib/machine.xwam
... standard:call_c/1  From /home/eschwartz/pharos/build/src/XSB/XSB/syslib/standard.xwam
... standard:call/1  From /home/eschwartz/pharos/build/src/XSB/XSB/syslib/standard.xwam
... setof:bfindall/4  From /home/eschwartz/pharos/build/src/XSB/XSB/syslib/setof.xwam
... setof:bagof1/3  From /home/eschwartz/pharos/build/src/XSB/XSB/syslib/setof.xwam
... setof:setof/3  From /home/eschwartz/pharos/build/src/XSB/XSB/syslib/setof.xwam
... concludeClassSizeGTE/1  From /data/shared/home/eschwartz/pharos/build/share/prolog/oorules/setup.xwam
... standard:call/1  From /home/eschwartz/pharos/build/src/XSB/XSB/syslib/standard.xwam
... reasonForwardAsManyTimesAsPossible/0  From /data/shared/home/eschwartz/pharos/build/share/prolog/oorules/setup.xwam
... standard:call_c/1  From /home/eschwartz/pharos/build/src/XSB/XSB/syslib/standard.xwam
... x_interp:_$call/1  From /home/eschwartz/pharos/build/src/XSB/XSB/syslib/x_interp.xwam
... x_interp:call_query/1  From /home/eschwartz/pharos/build/src/XSB/XSB/syslib/x_interp.xwam
... standard:call/1  From /home/eschwartz/pharos/build/src/XSB/XSB/syslib/standard.xwam
... standard:catch/3  From /home/eschwartz/pharos/build/src/XSB/XSB/syslib/standard.xwam
... x_interp:interpreter/0  From /home/eschwartz/pharos/build/src/XSB/XSB/syslib/x_interp.xwam
... loader:ll_code_call/3  From /home/eschwartz/pharos/build/src/XSB/XSB/syslib/loader.xwam
... loader:load_object_file/2  From /home/eschwartz/pharos/build/src/XSB/XSB/syslib/loader.xwam
... standard:call/1  From /home/eschwartz/pharos/build/src/XSB/XSB/syslib/standard.xwam
... standard:catch/3  From /home/eschwartz/pharos/build/src/XSB/XSB/syslib/standard.xwam

[Theresa Swift]

What OS are you using? (ctrl-c can act a little differently)

On Thu, Nov 1, 2018 at 11:12 AM Ed Schwartz edmcman@users.sourceforge.net
wrote:

I was testing this a little more, and I was wrong about the cause. It's
not whether the goal is specified via -e. I'm unclear why sometimes I'm
getting a break and sometimes the computation is being halted.

Here's an example where it works as expected:

^C[ Break (level 1) ]
1: ?- [ End break (level 1) ]

Here's an example where I press Ctrl-C and the computation stops:

C++Error[XSB/Runtime/P]: [Miscellaneous] Aborting...
Forward Continuation...
... machine:xsb_backtrace/1 From /home/eschwartz/pharos/build/src/XSB/XSB/syslib/machine.xwam
... standard:call_c/1 From /home/eschwartz/pharos/build/src/XSB/XSB/syslib/standard.xwam
... standard:call/1 From /home/eschwartz/pharos/build/src/XSB/XSB/syslib/standard.xwam
... setof:bfindall/4 From /home/eschwartz/pharos/build/src/XSB/XSB/syslib/setof.xwam
... setof:bagof1/3 From /home/eschwartz/pharos/build/src/XSB/XSB/syslib/setof.xwam
... setof:setof/3 From /home/eschwartz/pharos/build/src/XSB/XSB/syslib/setof.xwam
... concludeClassSizeGTE/1 From /data/shared/home/eschwartz/pharos/build/share/prolog/oorules/setup.xwam
... standard:call/1 From /home/eschwartz/pharos/build/src/XSB/XSB/syslib/standard.xwam
... reasonForwardAsManyTimesAsPossible/0 From /data/shared/home/eschwartz/pharos/build/share/prolog/oorules/setup.xwam
... standard:call_c/1 From /home/eschwartz/pharos/build/src/XSB/XSB/syslib/standard.xwam
... x_interp:_$call/1 From /home/eschwartz/pharos/build/src/XSB/XSB/syslib/x_interp.xwam
... x_interp:call_query/1 From /home/eschwartz/pharos/build/src/XSB/XSB/syslib/x_interp.xwam
... standard:call/1 From /home/eschwartz/pharos/build/src/XSB/XSB/syslib/standard.xwam
... standard:catch/3 From /home/eschwartz/pharos/build/src/XSB/XSB/syslib/standard.xwam
... x_interp:interpreter/0 From /home/eschwartz/pharos/build/src/XSB/XSB/syslib/x_interp.xwam
... loader:ll_code_call/3 From /home/eschwartz/pharos/build/src/XSB/XSB/syslib/loader.xwam
... loader:load_object_file/2 From /home/eschwartz/pharos/build/src/XSB/XSB/syslib/loader.xwam
... standard:call/1 From /home/eschwartz/pharos/build/src/XSB/XSB/syslib/standard.xwam
... standard:catch/3 From /home/eschwartz/pharos/build/src/XSB/XSB/syslib/standard.xwam

---

• [bugs:#242] https://sourceforge.net/p/xsb/bugs/242/ Ctrl-C stops the
  computation of goals specified by the -e option instead of creating a break*

Status: open
Group: Wish List
Created: Thu Nov 01, 2018 03:04 PM UTC by Ed Schwartz
Last Updated: Thu Nov 01, 2018 03:04 PM UTC
Owner: nobody

When XSB is processing a goal specified by the -e command line argument,
pressing Ctrl-C stops the computation instead of creating a break. Pressing
Ctrl-D at that point (or typing end_of_file.) does not resume the
computation, but exits XSB. I expected the behavior of Ctrl-C to be the
same as if I had typed the query at the prompt.

---

Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/xsb/bugs/242/

To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/

[Ed Schwartz]

Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic