[issue215555] Parser crashes for deeply nested list displays

2022-04-10 Thread admin


Change by admin :


--
github: None -> 33223

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue215555] Parser crashes for deeply nested list displays

2022-04-10 Thread admin


Change by admin :


___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue215555] Parser crashes for deeply nested list displays

2008-01-21 Thread Ralf Schmitt

Ralf Schmitt added the comment:

Ok, I've upped the limit to some very high value and tried to provoke a
stack overflow.
eval([*x+]*x) segfaults on my machine for x somewhere around 2
(linux, amd64). When setting MAXSTACK to 5000 eval([*x+]*x) works
for x = 333. So, I guess this should be safe guess (even for the BSDs,
which have a smaller default stack size).

BTW: The hardest part was recognizing that nothing gets rebuilt and that
more then parser.o depended on parser.h. Don't you have some kind of
automatic dependency tracking? Or am I missing some build tools?

Anyway, patch in http://bugs.python.org/issue1881


Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue21

___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue215555] Parser crashes for deeply nested list displays

2008-01-21 Thread Christian Heimes

Christian Heimes added the comment:

Parser/parser.h was not in the list of dependencies. I fixed it in r60151

--
nosy: +tiran


Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue21

___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue215555] Parser crashes for deeply nested list displays

2008-01-18 Thread Ralf Schmitt

Ralf Schmitt added the comment:

Ofcouse the problem was not logging, but I wanted to replay those
commands. This is where I got the error.


Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue21

___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue215555] Parser crashes for deeply nested list displays

2008-01-18 Thread Ralf Schmitt

Ralf Schmitt added the comment:

Well, I've been a victim of this one yesterday in a real world example.
I'm logging the repr of arguments to XMLRPC method calls and we happen
to use nested lists, which where deep enough to overflow that stack.

It's now 8 years later and I can live with the parser using 60K memory.
I think this limit should be upped a bit.

--
versions: +Python 2.6


Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue21

___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue215555] Parser crashes for deeply nested list displays

2008-01-18 Thread Guido van Rossum

Guido van Rossum added the comment:

Fine, submit a patch. Might as well open a new bug for the patch
(referring to this one for background).


Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue21

___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue215555] Parser crashes for deeply nested list displays

2008-01-17 Thread Ralf Schmitt

Changes by Ralf Schmitt:


--
nosy: +schmir


Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue21

___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com