[jira] Updated: (ZOOKEEPER-742) Deallocatng None on writes

2010-04-16 Thread Henry Robinson (JIRA)

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henry Robinson updated ZOOKEEPER-742:
-

Attachment: ZOOKEEPER-742.patch

This patch does a better job of handling references to Py_None - let me know if 
this helps.

> Deallocatng None on writes
> --
>
> Key: ZOOKEEPER-742
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-742
> Project: Zookeeper
>  Issue Type: Bug
>  Components: c client, contrib, contrib-bindings
>Affects Versions: 3.2.2, 3.3.0
> Environment: Redhat Enterprise 5.4 (python 2.4.3), Mac OS X 10.5.8 
> (python 2.5.1)
>Reporter: Josh Fraser
>Assignee: Henry Robinson
> Attachments: commands.py, foo.p, ZOOKEEPER-742.patch, 
> ZOOKEEPER-742.patch
>
>
> On write operations, getting:
> Fatal Python error: deallocating None
> Aborted
> This error happens on write operations only.  Here's the backtrace:
> Fatal Python error: deallocating None
> Program received signal SIGABRT, Aborted.
> 0x00383fc30215 in raise () from /lib64/libc.so.6
> (gdb) bt
> #0  0x00383fc30215 in raise () from /lib64/libc.so.6
> #1  0x00383fc31cc0 in abort () from /lib64/libc.so.6
> #2  0x2adbd0be8189 in Py_FatalError () from /usr/lib64/libpython2.4.so.1.0
> #3  0x2adbd0bc7493 in PyEval_EvalFrame () from 
> /usr/lib64/libpython2.4.so.1.0
> #4  0x2adbd0bcab66 in PyEval_EvalFrame () from 
> /usr/lib64/libpython2.4.so.1.0
> #5  0x2adbd0bcbfe5 in PyEval_EvalCodeEx () from 
> /usr/lib64/libpython2.4.so.1.0
> #6  0x2adbd0bcc032 in PyEval_EvalCode () from 
> /usr/lib64/libpython2.4.so.1.0
> #7  0x2adbd0be8729 in ?? () from /usr/lib64/libpython2.4.so.1.0
> #8  0x2adbd0be9bd8 in PyRun_SimpleFileExFlags () from 
> /usr/lib64/libpython2.4.so.1.0
> #9  0x2adbd0bf000d in Py_Main () from /usr/lib64/libpython2.4.so.1.0
> #10 0x00383fc1d974 in __libc_start_main () from /lib64/libc.so.6
> #11 0x00400629 in _start ()

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] Updated: (ZOOKEEPER-742) Deallocatng None on writes

2010-04-15 Thread Henry Robinson (JIRA)

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henry Robinson updated ZOOKEEPER-742:
-

Attachment: ZOOKEEPER-742.patch

Josh - are you able to apply this patch and try it out? It's not ready to be 
committed, but it adds a bit of defensive programming that should hopefully fix 
the error you're seeing. 

> Deallocatng None on writes
> --
>
> Key: ZOOKEEPER-742
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-742
> Project: Zookeeper
>  Issue Type: Bug
>  Components: c client, contrib, contrib-bindings
>Affects Versions: 3.2.2, 3.3.0
> Environment: Redhat Enterprise 5.4 (python 2.4.3), Mac OS X 10.5.8 
> (python 2.5.1)
>Reporter: Josh Fraser
> Attachments: commands.py, foo.p, ZOOKEEPER-742.patch
>
>
> On write operations, getting:
> Fatal Python error: deallocating None
> Aborted
> This error happens on write operations only.  Here's the backtrace:
> Fatal Python error: deallocating None
> Program received signal SIGABRT, Aborted.
> 0x00383fc30215 in raise () from /lib64/libc.so.6
> (gdb) bt
> #0  0x00383fc30215 in raise () from /lib64/libc.so.6
> #1  0x00383fc31cc0 in abort () from /lib64/libc.so.6
> #2  0x2adbd0be8189 in Py_FatalError () from /usr/lib64/libpython2.4.so.1.0
> #3  0x2adbd0bc7493 in PyEval_EvalFrame () from 
> /usr/lib64/libpython2.4.so.1.0
> #4  0x2adbd0bcab66 in PyEval_EvalFrame () from 
> /usr/lib64/libpython2.4.so.1.0
> #5  0x2adbd0bcbfe5 in PyEval_EvalCodeEx () from 
> /usr/lib64/libpython2.4.so.1.0
> #6  0x2adbd0bcc032 in PyEval_EvalCode () from 
> /usr/lib64/libpython2.4.so.1.0
> #7  0x2adbd0be8729 in ?? () from /usr/lib64/libpython2.4.so.1.0
> #8  0x2adbd0be9bd8 in PyRun_SimpleFileExFlags () from 
> /usr/lib64/libpython2.4.so.1.0
> #9  0x2adbd0bf000d in Py_Main () from /usr/lib64/libpython2.4.so.1.0
> #10 0x00383fc1d974 in __libc_start_main () from /lib64/libc.so.6
> #11 0x00400629 in _start ()

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] Updated: (ZOOKEEPER-742) Deallocatng None on writes

2010-04-15 Thread Josh Fraser (JIRA)

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Josh Fraser updated ZOOKEEPER-742:
--

Attachment: commands.py

Attached commands.py -- nothing private in the file.

> Deallocatng None on writes
> --
>
> Key: ZOOKEEPER-742
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-742
> Project: Zookeeper
>  Issue Type: Bug
>  Components: c client, contrib, contrib-bindings
>Affects Versions: 3.2.2, 3.3.0
> Environment: Redhat Enterprise 5.4 (python 2.4.3), Mac OS X 10.5.8 
> (python 2.5.1)
>Reporter: Josh Fraser
> Attachments: commands.py, foo.p
>
>
> On write operations, getting:
> Fatal Python error: deallocating None
> Aborted
> This error happens on write operations only.  Here's the backtrace:
> Fatal Python error: deallocating None
> Program received signal SIGABRT, Aborted.
> 0x00383fc30215 in raise () from /lib64/libc.so.6
> (gdb) bt
> #0  0x00383fc30215 in raise () from /lib64/libc.so.6
> #1  0x00383fc31cc0 in abort () from /lib64/libc.so.6
> #2  0x2adbd0be8189 in Py_FatalError () from /usr/lib64/libpython2.4.so.1.0
> #3  0x2adbd0bc7493 in PyEval_EvalFrame () from 
> /usr/lib64/libpython2.4.so.1.0
> #4  0x2adbd0bcab66 in PyEval_EvalFrame () from 
> /usr/lib64/libpython2.4.so.1.0
> #5  0x2adbd0bcbfe5 in PyEval_EvalCodeEx () from 
> /usr/lib64/libpython2.4.so.1.0
> #6  0x2adbd0bcc032 in PyEval_EvalCode () from 
> /usr/lib64/libpython2.4.so.1.0
> #7  0x2adbd0be8729 in ?? () from /usr/lib64/libpython2.4.so.1.0
> #8  0x2adbd0be9bd8 in PyRun_SimpleFileExFlags () from 
> /usr/lib64/libpython2.4.so.1.0
> #9  0x2adbd0bf000d in Py_Main () from /usr/lib64/libpython2.4.so.1.0
> #10 0x00383fc1d974 in __libc_start_main () from /lib64/libc.so.6
> #11 0x00400629 in _start ()

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] Updated: (ZOOKEEPER-742) Deallocatng None on writes

2010-04-15 Thread Josh Fraser (JIRA)

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Josh Fraser updated ZOOKEEPER-742:
--

Attachment: foo.p

attached the file since pasting lost the formatting

> Deallocatng None on writes
> --
>
> Key: ZOOKEEPER-742
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-742
> Project: Zookeeper
>  Issue Type: Bug
>  Components: c client, contrib, contrib-bindings
>Affects Versions: 3.2.2, 3.3.0
> Environment: Redhat Enterprise 5.4 (python 2.4.3), Mac OS X 10.5.8 
> (python 2.5.1)
>Reporter: Josh Fraser
> Attachments: foo.p
>
>
> On write operations, getting:
> Fatal Python error: deallocating None
> Aborted
> This error happens on write operations only.  Here's the backtrace:
> Fatal Python error: deallocating None
> Program received signal SIGABRT, Aborted.
> 0x00383fc30215 in raise () from /lib64/libc.so.6
> (gdb) bt
> #0  0x00383fc30215 in raise () from /lib64/libc.so.6
> #1  0x00383fc31cc0 in abort () from /lib64/libc.so.6
> #2  0x2adbd0be8189 in Py_FatalError () from /usr/lib64/libpython2.4.so.1.0
> #3  0x2adbd0bc7493 in PyEval_EvalFrame () from 
> /usr/lib64/libpython2.4.so.1.0
> #4  0x2adbd0bcab66 in PyEval_EvalFrame () from 
> /usr/lib64/libpython2.4.so.1.0
> #5  0x2adbd0bcbfe5 in PyEval_EvalCodeEx () from 
> /usr/lib64/libpython2.4.so.1.0
> #6  0x2adbd0bcc032 in PyEval_EvalCode () from 
> /usr/lib64/libpython2.4.so.1.0
> #7  0x2adbd0be8729 in ?? () from /usr/lib64/libpython2.4.so.1.0
> #8  0x2adbd0be9bd8 in PyRun_SimpleFileExFlags () from 
> /usr/lib64/libpython2.4.so.1.0
> #9  0x2adbd0bf000d in Py_Main () from /usr/lib64/libpython2.4.so.1.0
> #10 0x00383fc1d974 in __libc_start_main () from /lib64/libc.so.6
> #11 0x00400629 in _start ()

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira