Comment #15 on issue 434 by jtolds: With
PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=cpp, parent object deleted while
child still exists: causes segmentation fault
https://code.google.com/p/protobuf/issues/detail?id=434
Yay!!
--
You received this message because this project is configured to se
Updates:
Status: Fixed
Comment #14 on issue 434 by xiaof...@google.com: With
PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=cpp, parent object deleted while
child still exists: causes segmentation fault
https://code.google.com/p/protobuf/issues/detail?id=434
(No comment was entered for this
Updates:
Owner: jie...@google.com
Labels: FixedIn-2.6.0
Comment #13 on issue 434 by xiaof...@google.com: With
PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=cpp, parent object deleted while
child still exists: causes segmentation fault
http://code.google.com/p/protobuf/issues/detail?
Comment #12 on issue 434 by xiaof...@google.com: With
PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=cpp, parent object deleted while
child still exists: causes segmentation fault
http://code.google.com/p/protobuf/issues/detail?id=434
We are working a new release (2.6.0) right now and it will inclu
Comment #11 on issue 434 by tom.ritc...@gmail.com: With
PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=cpp, parent object deleted while
child still exists: causes segmentation fault
http://code.google.com/p/protobuf/issues/detail?id=434
Another xoogler here. Unfortunately convinced my team to use
Comment #10 on issue 434 by adam.gra...@upverter.com: With
PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=cpp, parent object deleted while
child still exists: causes segmentation fault
http://code.google.com/p/protobuf/issues/detail?id=434
A fix for this is crucial for us. I would be tempted to ro
Comment #9 on issue 434 by jtolds: With
PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=cpp, parent object deleted while
child still exists: causes segmentation fault
http://code.google.com/p/protobuf/issues/detail?id=434
:( does being a former one help? i can also do jumping jacks and make g+
pos
Comment #8 on issue 434 by xiaof...@google.com: With
PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=cpp, parent object deleted while
child still exists: causes segmentation fault
http://code.google.com/p/protobuf/issues/detail?id=434
Hi jtolds, thanks for offering the help, but unless you are a Goo
Updates:
Status: Accepted
Comment #6 on issue 434 by xiaof...@google.com: With
PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=cpp, parent object deleted while
child still exists: causes segmentation fault
http://code.google.com/p/protobuf/issues/detail?id=434
Reopened this issue as requeste
Comment #5 on issue 434 by igna...@corderi.com: With
PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=cpp, parent object deleted while
child still exists: causes segmentation fault
http://code.google.com/p/protobuf/issues/detail?id=434
Whats the status on this? I'm still getting segfaults and we are
Comment #4 on issue 434 by xiaof...@google.com: With
PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=cpp, parent object deleted while
child still exists: causes segmentation fault
http://code.google.com/p/protobuf/issues/detail?id=434
You can just keep an eye on the discussion group. When the new ve
Comment #3 on issue 434 by jtolds: With
PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=cpp, parent object deleted while
child still exists: causes segmentation fault
http://code.google.com/p/protobuf/issues/detail?id=434
any chance we could have this ticket reopened and then closed when the new
v
Updates:
Status: WontFix
Owner: xiaof...@google.com
Comment #2 on issue 434 by xiaof...@google.com: With
PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=cpp, parent object deleted while
child still exists: causes segmentation fault
http://code.google.com/p/protobuf/issues/detail?id=43
Comment #1 on issue 434 by xiaof...@google.com: With
PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=cpp, parent object deleted while
child still exists: causes segmentation fault
http://code.google.com/p/protobuf/issues/detail?id=434
A new version of C++ backed python implementation is under develo
14 matches
Mail list logo
