Re: [Zope-dev] disabling gc does not necessarily hide memory corruption

2001-12-19 Thread Toby Dickenson
On Wed, 19 Dec 2001 06:07:00 +1100, Anthony Baxter [EMAIL PROTECTED] wrote: For me, I run the ZEO server without GC (because that stops the stomped stack bug killing the ZEO server) Do you have reason to believe that this bug can affect the ZEO server? that would be very bad. Toby Dickenson

RE: [Zope-dev] disabling gc does not necessarily hide memory corruption

2001-12-19 Thread Brian Lloyd
Oh, ok, sorry for the misreport. It sounds then as if we need to fix whatever is causing the memory corruption that GC trips over. I dont know that we have a real good handle on what this is. I'm pretty sure we do. The stack estimation problems cause memory stomping, which happens to tend

Re: [Zope-dev] disabling gc does not necessarily hide memory corruption

2001-12-19 Thread Chris McDonough
It would be good if someone who is experiencing random crashes could confirm that the the new compiler package fixes their problem. - Original Message - From: Brian Lloyd [EMAIL PROTECTED] To: Chris McDonough [EMAIL PROTECTED]; [EMAIL PROTECTED] Cc: Anthony Baxter [EMAIL PROTECTED]; Zope

Re: [Zope-dev] disabling gc does not necessarily hide memorycorruption

2001-12-19 Thread Leonardo Rochael Almeida
On Wed, 2001-12-19 at 13:34, Chris McDonough wrote: It would be good if someone who is experiencing random crashes could confirm that the the new compiler package fixes their problem. I might risk losing a few more points with my sysadmin to test it (Hi daniduc :-) if there was an easily

Re: [Zope-dev] disabling gc does not necessarily hide memory corruption

2001-12-19 Thread Martijn Pieters
On Wed, Dec 19, 2001 at 05:24:58PM -0200, Leonardo Rochael Almeida wrote: On Wed, 2001-12-19 at 13:34, Chris McDonough wrote: It would be good if someone who is experiencing random crashes could confirm that the the new compiler package fixes their problem. I might risk losing a few more

Re: [Zope-dev] disabling gc does not necessarily hide memorycorruption

2001-12-19 Thread Chris McDonough
I just found out that the RestrictedPython package isn't actually yet fixed! Shane is working on it. He's sweating and I think I almost heard him curse once. ;-) So please hang tight and we'll let you know when it's safe to go in the water. Note that at the time that it's fixed, all that needs

Re: [Zope-dev] disabling gc does not necessarily hide memorycorruption

2001-12-19 Thread Leonardo Rochael Almeida
On Wed, 2001-12-19 at 18:02, Martijn Pieters wrote: [...] You can download files from CVS as a tarball. Just go to http://cvs.zope.org/Zope/lib/python/RestrictedPython and use the link at the bottom. Should I apply the ExtensionClass.h fix from CVS mentioned here in the list too? --

Re: [Zope-dev] disabling gc does not necessarily hide memorycorruption

2001-12-19 Thread Leonardo Rochael Almeida
Oh, and which branch should I get the tarball from? On Wed, 2001-12-19 at 18:20, Leonardo Rochael Almeida wrote: On Wed, 2001-12-19 at 18:02, Martijn Pieters wrote: [...] You can download files from CVS as a tarball. Just go to http://cvs.zope.org/Zope/lib/python/RestrictedPython and

Re: [Zope-dev] disabling gc does not necessarily hide memorycorruption

2001-12-19 Thread Chris McDonough
I'm not sure the ExtensionClass fix is baked yet, and there's not yet an overwhelming consensus that it helps stability, not to mention that I'm not sure how to install it, so no. ;-) I think you can use the trunk, no branch required. Hopefully the fixes will be merged soon. - Original

[Zope-dev] Precompiled binaries for Linux? (SuSE)

2001-12-19 Thread Joachim Werner
Hi! I have tried to compile psycopg on a SuSE Linux 7.0 system, but it I simply cannot get it done. Do you have some precompiled binaries you could post? Thanks a lot in advance! Joachim Werner ___ Zope-Dev maillist - [EMAIL PROTECTED]

Re: [Zope-dev] I'll wait then

2001-12-19 Thread Daniel Duclos
Em Quarta 19 Dezembro 2001 18:38, Leonardo Rochael Almeida escreveu: After reading this thread, my sysadmin (hi daniduc :-) just pointed a Hi Leo! =) gun at my head and said: When those guys say it's ready, you'll wait 24h and THEN you will try the fix :-) Aw, c'm'om, If I weren't

[Zope-dev] KeyError with __eq__

2001-12-19 Thread Joshua Lanza
I'm trying to publish an object without using content_publish_form (so directly invoking content_status_modify) and I'm getting Error Type: KeyError Error Value: __eq__ The only place I find __eq__ in the zope installation is in UserList.py, where it appears to be some kind of redefinition of

Re: [Zope-dev] OpenOffice and Zope ??

2001-12-19 Thread Joachim Werner
Hi! I don't have the resources to start something like that NOW, but I'd really like to see work on an OpenOffice integration: has anybody integrated/plans on intragration/experimented with OpenOffice and Zope ? YES. - OpenOffice as a HTML Editor / Web-Frontend for Zope I don't like that

Re: [Zope-dev] Precompiled binaries for Linux? (SuSE)

2001-12-19 Thread Joachim Werner
Hi! I finally managed to compile that beast. So I'll probably be the one to post binaries ASAP ... - Original Message - From: Joachim Werner [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Wednesday, December 19, 2001 9:37 PM Subject: [Zope-dev] Precompiled binaries

[Zope-dev] Strange error message: function attributes not accessible in restricted mode

2001-12-19 Thread Joachim Werner
Hi! I have two Zope 2.5 b2 installations on two seemingly identical machines, both with PostgreSQL, ZPsyCopDA, and DBObjects. In the DBObjects demo, I am getting THIS (see below) on one of the machines (the one with the slightly older installation). Very strange for me. What the hell is

Re: [Zope-dev] Re: Zope 2.4 crashes -- possible fix identified, other solutions also suggested

2001-12-19 Thread Joseph Wayne Norton
Matt - If possible, I would prefer to use a source Python 2.1.2 release with a source zope 2.4.4 ? bugfix release (or create my own from the 2.4 cvs branch) once the fixes are complete. We do not want to put a 2.5 release in production at this time. Thanks for the update. regards, - j At