scryer-prolog: thread 'main' panicked at 'index out of bounds when trying to load Logtalk

Yes, I ment Debug as in std::fmt::Debug with corresponding std::fmt::Display not as in debug vs. release build.

On Linux I get 1.000000…

I’m surprised by the difference between platforms. Rust is usually quite good about harmonizing these things.

Problem issue in c89324710708671586b70c7bcb9c005832d11060. Thanks! Notably, I’m able to run Logtalk’s standards compliance suite again.

Thanks for the latest fixes. With e4ea5476238e8669032b5ba5e0177048db2de4be, I now get:

?- {aliases(tester)}.
Killed: 9

No idea how to debug it this time.

Next bug, using 2b09cb44fed021a82440cd6f5076df4c1601c1fb:

?- write_canonical([a| _]), nl.
'.'(a _5521893)
   true.

g1:/opt/gupu/scryer-prolog> target/release/scryer-prolog -f
?- writeq(1e-5).
caught: error(syntax_error(incomplete_reduction),read_term/3:1)
?- writeq(1.0e-5).
0.00001   true.
?- 
g1:/opt/gupu/scryer-prolog> rustc --version
rustc 1.57.0 (f1edd0429 2021-11-29)

And then after rustupping:

g1:/opt/gupu/scryer-prolog> rustc --version
rustc 1.58.1 (db9d1b20b 2022-01-20)
g1:/opt/gupu/scryer-prolog> target/release/scryer-prolog -f
?- writeq(1.0e-5).
1e-5   true.
?- 

Interesting. I’m also on macOS (12.1) and I get (with 37e34c5209e48624d5e272c5b1dcf2bea7fdc1d3):

$ rustc --version
rustc 1.58.1
$ cargo run --release
   Compiling scryer-prolog v0.9.0 (/Users/pmoura/scryer-prolog)
    Finished release [optimized + debuginfo] target(s) in 1m 54s
     Running `target/release/scryer-prolog`
?- write(1.0e-5), nl.
1e-5
   true.

Could it be a locale issue?

Just compiled the latest git version (37e34c5209e48624d5e272c5b1dcf2bea7fdc1d3) of the rebis-dev branch. The puzzling exception is still there:

caught: error(syntax_error(incomplete_reduction),read_term/3:25)

It can be reproduced in a more simpler way:

?- {types(number)}.
caught: error(syntax_error(incomplete_reduction),read_term/3:25)
!     Unexpected failure while loading the code generated for the file:
!       /Users/pmoura/logtalk/library/types/number.lgt
!     Likely bug in the backend Prolog compiler. Please file a bug report.
false.

Instrumenting the Scryer adapter file, the number.lgt file is read fine up to included the end_of_file term. Further debugging shows that write_canonical/2 is writing a clause that the parser cannot read back:

?- read(T).
:-('$number#0.=~=#2'(_5654689,_5654690,_5654691),;(->(','('$number#0.epsilon#1'(_5654717,_5654691),<(abs(-(_5654689,_5654690)),*(100,_5654717))),true),<(abs(-(_5654689,_5654690)),*(1e-5,max(abs(_5654689),abs(_5654690)))))).
caught: error(syntax_error(incomplete_reduction),read/2:2)
?- read(T).
1e-5.
caught: error(syntax_error(incomplete_reduction),read/2:2)
?- write(1.0e-5), nl.
1e-5
   true.

Made some progress but now the logtalk os module load is failing.

Logtalk starts fine now. Thanks for the bug fixes. But trying to run some simple tests trigger a read error followed by a crash:

?- {aliases(tester)}.
caught: error(syntax_error(incomplete_reduction),read_term/3:25)
!     Unexpected failure while loading the code generated for the file:
!       /Users/pmoura/logtalk/library/types/number.lgt
!     Likely bug in the backend Prolog compiler. Please file a bug report.
Warning: initialization/1 failed for: user: '$lgt_logtalk_load'([types(termp),types(term),types(atomic),types(atom),types(number),types(float),types(integer),types(compound),types(listp),types(list),types(type)],[optimize(on)],'/Users/pmoura/logtalk/library/basic_types/',c(user,user,r(user,user,[],[])))
caught: error(syntax_error(incomplete_reduction),read_term/3:25)
!     Unexpected failure while loading the code generated for the file:
!       /Users/pmoura/logtalk/library/types/number.lgt
!     Likely bug in the backend Prolog compiler. Please file a bug report.
Warning: initialization/1 failed for: user: '$lgt_logtalk_load'([types(termp),types(term),types(atomic),types(atom),types(number),types(float),types(integer),types(compound),types(listp),types(list),types(type)],[optimize(on)],'/Users/pmoura/logtalk/library/basic_types/',c(user,user,r(user,user,[],[])))
caught: error(syntax_error(incomplete_reduction),read_term/3:25)
!     Unexpected failure while loading the code generated for the file:
!       /Users/pmoura/logtalk/library/types/number.lgt
!     Likely bug in the backend Prolog compiler. Please file a bug report.
Warning: initialization/1 failed for: user: '$lgt_logtalk_load'([types(termp),types(term),types(atomic),types(atom),types(number),types(float),types(integer),types(compound),types(listp),types(list),types(type)],[optimize(on)],'/Users/pmoura/logtalk/library/basic_types/',c(user,user,r(user,user,[],[])))
*     Reference to unknown object: list
*       while compiling object os
*       in file /Users/pmoura/logtalk/library/os/os.lgt between lines 2292-2336
*     
thread 'main' panicked at 'byte index 161 is out of bounds of `:-('$os#0.expand_path_chars#2'(_7374963,_7374964,_7374965),','(atom_chars(_7374963,_7374973),','(path_segments(_7374973,'.'(_7374987,_7374988)),','(;(->(=('.'($`', src/heap_print.rs:379:10
stack backtrace:
   0:        0x10afb84ba - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::hd4fa0e5fd1b0bae0
   1:        0x10afe758b - core::fmt::write::hd6db5571778cce6c
   2:        0x10afa845a - std::io::Write::write_fmt::hf56449a28d15bb2b
   3:        0x10afae805 - std::panicking::default_hook::{{closure}}::h2d0f2e1e91f96447
   4:        0x10afae3de - std::panicking::default_hook::hf6353a5dd2595e53
   5:        0x10afaee0a - std::panicking::rust_panic_with_hook::h916e420d7d249caa
   6:        0x10afb8dde - std::panicking::begin_panic_handler::{{closure}}::hc926ed443b77e590
   7:        0x10afb8617 - std::sys_common::backtrace::__rust_end_short_backtrace::hf8832c1005df0617
   8:        0x10afae8f3 - _rust_begin_unwind
   9:        0x10affba2f - core::panicking::panic_fmt::hedd127944bd71c57
  10:        0x10affbc4d - core::str::slice_error_fail::hfaf65b4c7b4168e8
  11:        0x10ab6cd8f - core::str::traits::<impl core::slice::index::SliceIndex<str> for core::ops::range::RangeFrom<usize>>::index::h51569a88cbbbb36b
                               at /opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_lang_rust/rust/work/rustc-1.58.1-src/library/core/src/str/traits.rs:364:21
  12:        0x10ab6cd8f - core::str::traits::<impl core::ops::index::Index<I> for str>::index::h875189113eef7522
                               at /opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_lang_rust/rust/work/rustc-1.58.1-src/library/core/src/str/traits.rs:64:9
  13:        0x10ab6cd8f - <scryer_prolog::heap_print::PrinterOutputter as scryer_prolog::heap_print::HCValueOutputter>::range_from::h779951e815fc30b1
                               at /Users/pmoura/scryer-prolog/src/heap_print.rs:379:10
  14:        0x10ab6cd8f - scryer_prolog::heap_print::HCPrinter<Outputter>::ambiguity_check::h64bb7e64607eebbb
                               at /Users/pmoura/scryer-prolog/src/heap_print.rs:542:20
  15:        0x10ab6cd8f - scryer_prolog::heap_print::HCPrinter<Outputter>::handle_heap_term::h1e4f5fd11ef08616
                               at /Users/pmoura/scryer-prolog/src/heap_print.rs:1450:21
  16:        0x10ab6ea65 - scryer_prolog::heap_print::HCPrinter<Outputter>::print::hd93e415169da4ab6
                               at /Users/pmoura/scryer-prolog/src/heap_print.rs:1510:25
  17:        0x10abd8f2b - scryer_prolog::machine::system_calls::<impl scryer_prolog::machine::Machine>::write_term::h34cb85bf714baf5f
                               at /Users/pmoura/scryer-prolog/src/machine/system_calls.rs:4900:22
  18:        0x10abd8f2b - scryer_prolog::machine::dispatch::<impl scryer_prolog::machine::Machine>::dispatch_loop::ha980dc60645d6aca
                               at /Users/pmoura/scryer-prolog/src/machine/dispatch.rs:4338:52
  19:        0x10abd8f2b - scryer_prolog::machine::Machine::run_module_predicate::hbec72e701763ef83
                               at /Users/pmoura/scryer-prolog/src/machine/mod.rs:188:24
  20:        0x10abfe807 - scryer_prolog::machine::Machine::run_top_level::h926d89ad9e4c82a6
                               at /Users/pmoura/scryer-prolog/src/machine/mod.rs:282:9
  21:        0x10aadd33f - scryer_prolog::main::hcc0438faf361ffec
                               at /Users/pmoura/scryer-prolog/src/bin/scryer-prolog.rs:10:5
  22:        0x10aade046 - core::ops::function::FnOnce::call_once::h7186c7639690107a
                               at /opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_lang_rust/rust/work/rustc-1.58.1-src/library/core/src/ops/function.rs:227:5
  23:        0x10aade046 - std::sys_common::backtrace::__rust_begin_short_backtrace::h239a271907c8db3d
                               at /opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_lang_rust/rust/work/rustc-1.58.1-src/library/std/src/sys_common/backtrace.rs:123:18
  24:        0x10aadd43c - std::rt::lang_start::{{closure}}::hce6a7b59d9b7dbbb
                               at /opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_lang_rust/rust/work/rustc-1.58.1-src/library/std/src/rt.rs:145:18
  25:        0x10afa1ad5 - std::rt::lang_start_internal::he7843d316f67a515
  26:        0x10aadd429 - <unknown>
                               at /opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_lang_rust/rust/work/rustc-1.58.1-src/library/core/src/result.rs:1295:23
✘-101 ~ 

I will try to isolate the read error. But meanwhile I hope the crash stack trace would be useful.