It was the "~/.pil/rc” file - trashing it fixed the issue. Thanks for your
help!
> On Feb 13, 2022, at 7:30 AM, Alexander Burger wrote:
>
> On Sun, Feb 13, 2022 at 07:12:57AM -0500, Todd Roth wrote:
>> “/home/xxx/pil21/pil +” fails with segfault
>
> Another idea: In debug mode "~/.pil/rc" i
On Sun, Feb 13, 2022 at 07:12:57AM -0500, Todd Roth wrote:
> “/home/xxx/pil21/pil +” fails with segfault
Another idea: In debug mode "~/.pil/rc" is loaded. Perhaps it exists and
contains some garbage?
☺/ A!ex
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
On Sun, Feb 13, 2022 at 07:12:57AM -0500, Todd Roth wrote:
> Relative e.g. "../pil21/pil +” works fine from any directory
>
> “/home/xxx/pil21/pil +” fails with segfault
>
> It’s clearly something with my existing user account. I setup another user
> account, installed picolisp locally, and do n
Relative e.g. "../pil21/pil +” works fine from any directory
“/home/xxx/pil21/pil +” fails with segfault
It’s clearly something with my existing user account. I setup another user
account, installed picolisp locally, and do not get the segfault. I’ll keep
digging.
> On Feb 13, 2022, at 1:33
Hi Todd,
On Sat, Feb 12, 2022 at 09:04:32PM -0500, Todd Roth wrote:
> When invoking pil in Debug mode from my source directory using ‘pil +’ I get a
> a segfault ->> 'Segmentation fault (core dumped)’
>
> When I cd into the pil21 src directory and invoke the binary directly using
> ‘./pil +’ I no
I’m running a local installation of picolisp (pil21 ver 22.2.11) on Ubuntu
20.04.3
When invoking pil in Debug mode from my source directory using ‘pil +’ I get a
a segfault ->> 'Segmentation fault (core dumped)’
When I cd into the pil21 src directory and invoke the binary directly using
‘./pi
