Tomasz Lipski <[email protected]> writes: > 2009/5/25 Jan Rychter <[email protected]>: > >> Incidentally, it seems the SBCL profiler is completely broken on at >> least Mac OS X and Linux. I get all sorts of corruption, crashes and >> errors once it is enabled. >> >> What is more worrying is that testing my application with siege also >> sometimes produces SBCL memory corruption :-/ > > I have encountered memory corruption too, but only when using > clsql-postgresql and quite fresh (>1.0.25.7) sbcl. I would have to > reboot to check the exact version, but switching to > clsql-postgresql-socket or sbcl 1.0.25.7 remedies the problem. > > Though I haven't done siege/grinder tests yet.
Hmm -- I'm using 1.0.28 and have had the same kinds of problems on both Mac OS X and Linux. Additionally it seems that there are some issues with UTF-8 which make SBCL explode in a giant fireball. As an example, I can make SBCL explode just by connecting from Emacs to a running swank server (both ends have utf-8-unix encoding specified). Interesting. Perhaps I should try downgrading. --J. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "weblocks" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/weblocks?hl=en -~----------~----~----~----~------~----~------~--~---
