Wow. I'm having _so_ much fun with 2.6. I'm now seeing a reproducible
segfault on startup.
Program received signal SIGSEGV, Segmentation fault.
0xfe4517c8 in accessed (self=0xedbe58) at ZODB/cPersistence.c:160
160 self-ring.next-prev = self-ring.prev;
(gdb) p self
$1 =
More information: I don't see the failure with a fresh Data.fs. The
Data.fs in question is my 2.5 one. I'm running the current HEAD of
Zope-2_6-branch. I packed the Data.fs, the same result.
I've added a simple function to 2.6's cPersistence.c:
static void
ringcheck(CPersistentRing *start)
{
Hi all,
The problem I describe here does NOT appear with Zope
2.6.1, nor Zope 2.6.2b4, only with Zope 2.7.
I installed Zope 2.7 with CMF 1.4, Plone 1.1alpha2
and TranslationService 0.4. When I create a Plone site (called dice here) Ive
got the following error:
AssertionError
On Friday 25 July 2003 08:30, Anthony Baxter wrote:
More information: I don't see the failure with a fresh Data.fs. The
Data.fs in question is my 2.5 one.
Do you have any custom persistent extension classes stored in that Data.fs
that might not have been updated to the 2.6 persistence C API?
Toby Dickenson wrote
On Friday 25 July 2003 08:30, Anthony Baxter wrote:
More information: I don't see the failure with a fresh Data.fs. The
Data.fs in question is my 2.5 one.
Do you have any custom persistent extension classes stored in that Data.fs
that might not have been updated to
*sigh*
So I tried a fresh checkout on a different box, no crash.
Completely nuked old checkout (which was a new checkout
last night), checked out again, rebuilt, no crash.
Beats me. I'm going to blame the electrician who took out
power to our floor this morning, because it's that or
cosmic
Fred L. Drake, Jr. wrote:
- Use a Python-like sequence unpacking syntax. This is probably most
comfortable to template authors who are Python programmers first,
and web guys (or gals!) second.
-0 for feature creap
- Use the namespace qualifiers to get an adapter to handle converting
Hi folks,
Since we started configuration and installation geddon on Zope 2 (which
has resulted in Zope 2.7), we've made a number of improvements in the
flexibility of file placement behaviors:
- You can specify in the config file where you want your
lock and pid files to be placed.
- You can
Jean Baltus wrote:
Hi all,
The problem I describe here does NOT appear with Zope 2.6.1, nor Zope
2.6.2b4, only with Zope 2.7.
I installed Zope 2.7 with CMF 1.4, Plone 1.1alpha2 and
TranslationService 0.4. When I create a Plone site (called dice here)
Ive got the following error:
...
*
Chris McDonough writes:
I propose that we add two more options to the config file:
import-directory
extensions-directory
I'd like to suggest that we call these imports and extensions, to
be parallel with the products multikey.
For products, we use the specified directories to add to
WELCOME TO THE ZOPE 3 NEWSLETTER: ISSUE 9 (25 JULY 2003)
Welcome to the ninth Zope 3 newsletter. Information about Zope 3
and newsletter contributions and suggestions can be found at the
bottom of this newsletter.
GLOSSARY FOR THE UNINITIATED
Encounter a term in this newsletter you
I only use 2 because it's there :-) Thinking more about it, it
occurs to me that python expressions in TALES provide a huge hole
in the separation of presentation from logic.
My view is that embedding logic in presentation isn't quite the right
thing to avoid. Consider how much logic goes into
Godefroid Chapelle wrote:
To summarize, as message ids translation for attributes was added, 2.7
and 3 are working according to the doc/spec,
but 2.7 breaks backward compatibility to 2.6.1.
This leads to the following question : do we (1) accept this rupture in
i18n:attributes management or
Anthony Baxter wrote:
Is it possible that there's a C code product that's not been updated? How would I
figure out what it might be?
Are you running the DynPersist extension from ZPatterns? That would
need to be recompiled.
Also note that python setup.py build doesn't reliably rebuild the
On Fri, 2003-07-25 at 10:30, Fred L. Drake, Jr. wrote:
Chris McDonough writes:
I propose that we add two more options to the config file:
import-directory
extensions-directory
I'd like to suggest that we call these imports and extensions, to
be parallel with the products
Chris McDonough writes:
Actually, both of these directories have historically worked in much
the same way as the Products package does.
Ok, well, that's still not hard to do; we just add the bootstrap
directories to each of the lists once we've read the config.
A software home may have
On Fri, Jul 25, 2003 at 09:52:14AM -0400, Chris McDonough wrote:
- You can specify in the config file any number of
Products directory paths and these will be knitted
together into the Products pseudopackage.
Sounds good. One thing to watch out for - this needs to be tested
with CMF,
[Anthony Baxter]
*sigh*
So I tried a fresh checkout on a different box, no crash.
Completely nuked old checkout (which was a new checkout
last night), checked out again, rebuilt, no crash.
Beats me. I'm going to blame the electrician who took out
power to our floor this morning, because
Chris McDonough wrote:
Update of /cvs-repository/Zope/lib/python/TAL
In directory cvs.zope.org:/tmp/cvs-serv15492/lib/python/TAL
Modified Files:
TALGenerator.py
Log Message:
Merge TAL i18n fixes which break CMF to HEAD from 2.7 branch.
The agreement Jim was basically that this backward
Hmm. Without this fix, many CMFDefault (and possibly CMFCore) skins
don't work. Is there a way to fix the offending CMF skins so that it
works under Zope versions both with this fix and without (so we don't
need two versions of CMF)? More importantly, is anyone willing to
actually do this work?
Tim Peters wrote
Jeremy and I saw cases of ring corruption while putting together the
experimental ZODB 3.3, but they were 100% reproducible on all platforms, and
turned out to have clear causes (some of the C objects we backported from
ZODB4 were getting ghostified by the ZODB4 code without
21 matches
Mail list logo
