Hi,
I have confirmed that this results in an immediate crash when I use Pico
Lisp 2.3.6 or newer on my Mac. However, I'm not sure what I can do
further to reveal what causes the memory to be overwritten. Any ideas?
/Jon
On 6/26/09 10:13 AM, Alexander Burger wrote:
Hi all,
now Randall and I
Thomas: >>I think there was some other problem mentioned on this
mailing list that was caused by -O2...<<
Yes, don't compile pico lisp on a Ubuntu version newer than Feisty,
the result is highly unstable with O2, seems to be working with O1
though.
In any case I just don't compile pico lisp on ne
Hi all,
Randall kept urging me to make PicoLisp more independent of the case
sensitivity of underlying file systems. He is now a happy Mac user, and
the Mac OS file system is case insensitive (shudder).
As far as I see, there are two places where PicoLisp depends on the case
of file names:
1. In
On Sat, Jul 18, 2009 at 03:08:34PM +0200, Henrik Sarvell wrote:
> Yes, don't compile pico lisp on a Ubuntu version newer than Feisty,
> the result is highly unstable with O2, seems to be working with O1
> though.
Hmm, I do not think that the problems here have to do with the C
compiler.
It rather
This has nothing to do with this Mac problem, it's an old thing which
breaks the functioning of pico lisp itself, while doing very basic
stuff, as noted, it's been discussed at length before.
/Henrik
On Sat, Jul 18, 2009 at 4:52 PM, Alexander Burger wrote:
> On Sat, Jul 18, 2009 at 03:08:34PM +0
On Sat, Jul 18, 2009 at 05:06:50PM +0200, Henrik Sarvell wrote:
> This has nothing to do with this Mac problem, it's an old thing which
True. One more reason to swicht to the 64-bit assembly version, which
does not depend on any obscure compiler ;-)
--
UNSUBSCRIBE: mailto:picol...@software-lab.de
