Hi!
I started it under Linux, this time. Same metakit version 2.4.9.2. I used
gdb to get a bit more infos:
[EMAIL PROTECTED]:~/.PyDS/tools$ gdb python2.2
GNU gdb 2002-04-01-cvs
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-linux"...(no debugging symbols found)...
(gdb) run
Starting program: /usr/bin/python2.2
(no debugging symbols found)...(no debugging symbols found)...[New Thread 1024 (LWP
7436)]
(no debugging symbols found)...(no debugging symbols found)...
Python 2.2.1 (#1, Sep 7 2002, 14:34:30)
[GCC 2.95.4 20011002 (Debian prerelease)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
>>> import metakit
(no debugging symbols found)...(no debugging symbols found)...
db>>> db = metakit.storage()
>>> table = db.getas('B[zeile[key:S,value:S]]')
>>> btable = table.blocked()
>>> stable = btable.ordered(1)
>>> stable.append(key='blah',value='blubb')
(no debugging symbols found)...(no debugging symbols found)...
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1024 (LWP 7436)]
0x402278ae in c4_HandlerSeq::NthHandler ()
from /usr/lib/python2.2/site-packages/Mk4py.so
Does this help to pin down the problem? Any hints on what I could do to
help find this one?
It's a show-stopper for me, as I need blocked and ordered views because of
the expected volume of records in an application I am playing around currently
with.
bye, Georg
_______________________________________________
metakit mailing list - [EMAIL PROTECTED]
http://www.equi4.com/mailman/listinfo/metakit
