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 AM, Alexander Burger <a...@software-lab.de> wrote: > > 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 longer get the segfault. >> >> I have /home/xxx/pil21 added to PATH in .profile > > This should be fine. What happens if you call it with a relative or absolute > path, e.g. "../pil21/pil +" or "/home/xxx/pil21/pil +"? > > ☺/ A!ex > > -- > UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
