[issue38042] Crash on double list(lxml.etree.iterparse(f)) Edit
New submission from Alexander Kurakin :
I have a crash in Python 3.x environments and don't have in 2.7.
===
Crashes in:
Python 3.7.4, Anaconda, Linux 64bit, lxml 4.3.3
OR
Python 3.7.4, Anaconda, Linux 64bit, lxml 4.4.1
OR
Python 3.6.5, Gentoo Linux 64bit, lxml 4.3.3
test.py:
import lxml
import lxml.etree
with open('test.xml', 'rb') as f:
list(
lxml.etree.iterparse(f)
)
# Traceback (most recent call last):
# File "test.py", line 18, in
# lxml.etree.iterparse(f)
# File "src/lxml/iterparse.pxi", line 209, in lxml.etree.iterparse.__next__
# File "src/lxml/iterparse.pxi", line 194, in lxml.etree.iterparse.__next__
# File "src/lxml/iterparse.pxi", line 225, in
lxml.etree.iterparse._read_more_events
# File "src/lxml/parser.pxi", line 1380, in lxml.etree._FeedParser.close
# Segmentation fault
list(
lxml.etree.iterparse(f)
)
test.xml:
(or any else)
GDB's backtrace see in attachment.
===
Doesn't crash in:
Python 2.7.15, Gentoo Linux 64bit, lxml 4.3.3
# Traceback (most recent call last):
# File "test.py", line 19, in
# lxml.etree.iterparse(f)
# File "src/lxml/iterparse.pxi", line 209, in lxml.etree.iterparse.__next__
#File "/home/sasha/_lxml-bug/test.xml", line 0
lxml.etree.XMLSyntaxError: no element found
===
See also: https://bugs.launchpad.net/lxml/+bug/1833050
--
files: bt.txt
messages: 351222
nosy: kuraga
priority: normal
severity: normal
status: open
title: Crash on double list(lxml.etree.iterparse(f)) Edit
type: crash
versions: Python 3.6, Python 3.7
Added file: https://bugs.python.org/file48595/bt.txt
___
Python tracker
<https://bugs.python.org/issue38042>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38042] Crash on double list(lxml.etree.iterparse(f))
Change by Alexander Kurakin : -- title: Crash on double list(lxml.etree.iterparse(f)) Edit -> Crash on double list(lxml.etree.iterparse(f)) ___ Python tracker <https://bugs.python.org/issue38042> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38042] Crash on double list(lxml.etree.iterparse(f))
Alexander Kurakin added the comment: Yes, I do. Please read all. 1) According to https://bugs.launchpad.net/lxml/+bug/1833050 (by lxml author's opinion) it's not a lxml bug. 2) I wouldn't said that but according to backtrace we have crash at Python-time. 3) Moreover crash existence depends on Python version! Thanks. -- ___ Python tracker <https://bugs.python.org/issue38042> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38042] Crash on double list(lxml.etree.iterparse(f))
Alexander Kurakin added the comment: Ok, thanks! Good that I was too lazy to open bug in June because our colleague did it better then me :) Seems like the fix doesn't present in current 3.7 version (3.7.4). Will try in 3.7.5 and will close UPD: Oh, closed? Ok. But *no*, it's not fixed in current 3.7 version (in master - yes). I wrote: 3.7.4. Let's check each other instead of... Sorry. Thanks. -- versions: +Python 3.7 ___ Python tracker <https://bugs.python.org/issue38042> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38638] Backtrace of exit phase of context managers
New submission from Alexander Kurakin :
class CM:
def __init__(self):
pass
def __enter__(self):
return self
def __exit__(self, exc_type, exc_val, exc_tb):
raise RuntimeError()
if __name__ == '__main__':
with CM() as cm:
print('Hello')
$ python3 cm.py
Hello
Traceback (most recent call last):
File "cm.py", line 14, in
print('Hello') # <--
File "cm.py", line 10, in __exit__
raise RuntimeError()
RuntimeError
Is it correct that print presents in backtrace? Well it's the last line but...
Thanks.
--
components: Interpreter Core
messages: 355698
nosy: kuraga
priority: normal
severity: normal
status: open
title: Backtrace of exit phase of context managers
type: behavior
versions: Python 3.6
___
Python tracker
<https://bugs.python.org/issue38638>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue25538] Traceback from __exit__ method is misleading
Change by Alexander Kurakin : -- nosy: +kuraga ___ Python tracker <https://bugs.python.org/issue25538> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42372] A crash in do_richcompare
New submission from Alexander Kurakin : Sometimes test.py causes a crash in 3.7.9 (and lower to 2018 year or more) on Linux. See also: https://github.com/pandas-dev/pandas/issues/21968 -- components: Interpreter Core files: issue.zip messages: 381113 nosy: kuraga priority: normal severity: normal status: open title: A crash in do_richcompare type: crash versions: Python 3.7 Added file: https://bugs.python.org/file49603/issue.zip ___ Python tracker <https://bugs.python.org/issue42372> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42372] A crash in do_richcompare
Alexander Kurakin added the comment: Thanks for reply! Is it call of NULL? If so, shoudn't do_richcompare check it? -- ___ Python tracker <https://bugs.python.org/issue42372> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42372] A crash in do_richcompare
Alexander Kurakin added the comment: Ok, close. -- stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue42372> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
