Re: [Zope-dev] Re: large files and --pymalloc on the new release? (was Re: no more SIG11 ...)

2002-01-17 Thread Dario Lopez-Kästen

From: Chris McDonough [EMAIL PROTECTED]
 Leonardo Rochael Almeida wrote:
snip

  Also, what about the --pymalloc? Is the binary Zope Python going to be
  compiled with it? should I still fear it?

 Dunno.  Was it compiled in before?  Isn't this an issue that is solved
 in a roundabout way by not having stack pointer computation bugs in the
 first place?  I'm not sure how all of these bugs interact with each other.

  We almost lost a big client and almost got a lawsuit because we were
  bitten by both (or would that be three: RestrictedCompiler, ceval and
  --pymalloc?) bugs at the same time and took a long time to figure out
  how to work around them.

 Sorry to hear that.


Is there a way to perform some tests or is there a testsuite that can be
used to stress test these issues? I too got bitten by these bugs + assorted
thread related errors, which has cost us very dearly in our project in terms
of both time, additional costs and unexpected hardware investments due to
change of deployment platform, so I *really* would like to have some way of
being able to confirm if these bugs are dealt with or no. I am not sure
there are any consistent tests for this, though, so hints on what to look
out for are equally appreciated.

thnks,

/dario

- 
Dario Lopez-Kästen Systems Developer  Chalmers Univ. of Technology
[EMAIL PROTECTED]  ICQ will yield no hitsIT Systems  Services



___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )



[Zope-dev] Re: large files and --pymalloc on the new release? (was Re: no more SIG11 ...)

2002-01-16 Thread Chris McDonough

Leonardo Rochael Almeida wrote:

 Will the binary Linux release include large file support?
 In other words, can I have a  2G Data.fs?


Hmmm.. I dont think the Zope 2.5b4 Linux binary is built this way, but 
in both Zope 2.4.4 and 2.5.0 it probably should be.  We'd probably need 
someone to confirm that this doesn't cause problems on older (2.0, 2.2) 
Linux systems.  FWIW, I built Python 2.1.2 with large file support on 
Linux 2.4 using the instructions on the posix-largefiles doc page in the 
Python docs without a problem.

 Also, what about the --pymalloc? Is the binary Zope Python going to be
 compiled with it? should I still fear it?


Dunno.  Was it compiled in before?  Isn't this an issue that is solved 
in a roundabout way by not having stack pointer computation bugs in the 
first place?  I'm not sure how all of these bugs interact with each other.

 We almost lost a big client and almost got a lawsuit because we were
 bitten by both (or would that be three: RestrictedCompiler, ceval and
 --pymalloc?) bugs at the same time and took a long time to figure out
 how to work around them.

Sorry to hear that.

- C


___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )