[issue16806] col_offset is -1 and lineno is wrong for multiline string expressions
Ivailo Karamanolev added the comment:
What's the status on this? Anything preventing it getting fixed? Still the same
in 3.6.1:
>>> import ast
>>> ast.parse("""'''foo\n'''""").body[0].value.col_offset
-1
--
nosy: +karamanolev
___
Python tracker
<http://bugs.python.org/issue16806>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23187] Segmentation fault, possibly asyncio related
New submission from Ivailo Karamanolev: I have a program that's running Tornado on top of asyncio and uses mysql-connector-python to monitor a set of HTTP servers and save the status to MySQL. Initially I ran it with the current version of Python in the Ubuntu 14.04 repos, that's 3.4.0 and started getting segmentation faults after keeping it running for a few days. I compiled and installed 3.4.2 and the same thing keeps happening, with the same stack trace (per gdb). Running it with and without gdb attached gives the same results - seg fault after 3-4 days of running. The machine is running on a Xeon with ECC memory and doesn't show signs of illness otherwise, so it's probably not a hardware problem. Also, it's happening consistently when the programs runs for 3-4 days, with or without a system reboot. Program received signal SIGSEGV, Segmentation fault. 0x00471ed7 in subtype_dealloc (self=0x716a3860) at Objects/typeobject.c:1128 1128_PyObject_GC_UNTRACK(self); Stack trace: #0 0x00471ed7 in subtype_dealloc (self=0x716a3860) at Objects/typeobject.c:1128 #1 0x004563f4 in dict_dealloc (mp=0x7fffe95444c8) at Objects/dictobject.c:1383 #2 0x00472140 in subtype_dealloc (self=0x7fffe8e1fcf8) at Objects/typeobject.c:1157 #3 0x0058ad22 in frame_dealloc (f=0x1145258) at Objects/frameobject.c:429 #4 0x00588fd7 in gen_send_ex (gen=gen@entry=0x7fffe8c5cea0, gen=gen@entry=0x7fffe8c5cea0, exc=0, arg=arg@entry=0x0) at Objects/genobject.c:145 #5 _PyGen_Send (gen=gen@entry=0x7fffe8c5cea0, arg=arg@entry=0x87fec0 <_Py_FalseStruct>) at Objects/genobject.c:158 #6 0x004da329 in PyEval_EvalFrameEx (f=f@entry=0x11faaf8, throwflag=throwflag@entry=0) at Python/ceval.c:1906 #7 0x00588e5c in gen_send_ex (gen=gen@entry=0x7fffe8c5ccf0, gen=gen@entry=0x7fffe8c5ccf0, exc=0, arg=arg@entry=0x71bb6420) at Objects/genobject.c:104 #8 _PyGen_Send (gen=gen@entry=0x7fffe8c5ccf0, arg=arg@entry=0x87fec0 <_Py_FalseStruct>) at Objects/genobject.c:158 #9 0x004da329 in PyEval_EvalFrameEx (f=f@entry=0x10daa48, throwflag=throwflag@entry=0) at Python/ceval.c:1906 #10 0x00588e5c in gen_send_ex (gen=gen@entry=0x7fffe8c5cc18, gen=gen@entry=0x7fffe8c5cc18, exc=0, arg=arg@entry=0x102aac8) at Objects/genobject.c:104 #11 _PyGen_Send (gen=gen@entry=0x7fffe8c5cc18, arg=arg@entry=0x87fec0 <_Py_FalseStruct>) at Objects/genobject.c:158 #12 0x004da329 in PyEval_EvalFrameEx (f=f@entry=0x10da7f8, throwflag=throwflag@entry=0) at Python/ceval.c:1906 #13 0x00588e5c in gen_send_ex (gen=0x716b65a0, gen=0x716b65a0, exc=0, arg=) at Objects/genobject.c:104 #14 _PyGen_Send (gen=0x716b65a0, arg=) at Objects/genobject.c:158 #15 0x004d9d0b in call_function (oparg=, pp_stack=0x7fffd290) at Python/ceval.c:4221 #16 PyEval_EvalFrameEx (f=f@entry=0x10da568, throwflag=throwflag@entry=0) at Python/ceval.c:2836 #17 0x004d28d4 in PyEval_EvalCodeEx (_co=0x71e0c030, globals=, locals=, args=, argcount=3, kws=0x12e38b8, kwcount=0, defs=0x71e0a8e0, defcount=2, kwdefs=0x0, closure=0x71e10588) at Python/ceval.c:3585 #18 0x004d8e75 in fast_function (nk=, na=3, n=3, pp_stack=0x7fffd490, func=0x71e122f0) at Python/ceval.c:4341 #19 call_function (oparg=, pp_stack=0x7fffd490) at Python/ceval.c:4259 #20 PyEval_EvalFrameEx (f=f@entry=0x12e3708, throwflag=throwflag@entry=0) at Python/ceval.c:2836 #21 0x004d28d4 in PyEval_EvalCodeEx (_co=0x71e0c0c0, globals=, locals=locals@entry=0x0, args=args@entry=0x7fffeae8a720, argcount=2, kws=kws@entry=0x0, kwcount=kwcount@entry=0, defs=defs@entry=0x0, defcount=defcount@entry=0, kwdefs=0x0, closure=0x0) at Python/ceval.c:3585 #22 0x0058c67c in function_call (func=0x71e12378, arg=0x7fffeae8a708, kw=0x0) at Objects/funcobject.c:632 #23 0x0042686a in PyObject_Call (func=func@entry=0x71e12378, arg=arg@entry=0x7fffeae8a708, kw=kw@entry=0x0) at Objects/abstract.c:2067 #24 0x004d48a4 in ext_do_call (nk=, na=1, flags=, pp_stack=0x7fffd760, func=0x71e12378) at Python/ceval.c:4558 #25 PyEval_EvalFrameEx (f=f@entry=0x145ac48, throwflag=throwflag@entry=0) at Python/ceval.c:2876 #26 0x004d9e82 in fast_function (nk=, na=1, n=1, pp_stack=0x7fffd8a0, func=0x71e2d488) at Python/ceval.c:4331 #27 call_function (oparg=, pp_stack=0x7fffd8a0) at Python/ceval.c:4259 #28 PyEval_EvalFrameEx (f=f@entry=0x11aee28, throwflag=throwflag@entry=0) at Python/ceval.c:2836 #29 0x004d9e82 in fast_function (nk=, na=1, n=1, pp_stack=0x7fffd9f0, func=0x71bc1400) at Python/ceval.c:4331 #30 call_function (oparg=, pp_stack=0x7fffd9f0) at Python/ceval.c:4259 #31 PyEval_EvalFrameEx (f=f@entry=0x10d9c68, throwflag=throwflag@entry=0) at Python/ceval.c:2836 #32 0x004d9e82 in fast_function (nk=, na=1, n=1, pp_stack=0x7
[issue23187] Segmentation fault, possibly asyncio related
Ivailo Karamanolev added the comment: Running out of memory is unlikely. There are many other processes running on the machine and none of them show signs of memory issues. In addition, the munin memory usage reporting doesn't show signs of steady growing or drops when the process crashes (munin screenshot attached). 3.4.0 and 3.4.2 on all runs showed exactly the same stack trace. AFAIK mysql-connector-python is pure Python, so even if the problem was there, I think it's still Python core. I'm not 100% on this though. -- Added file: http://bugs.python.org/file37636/Screenshot 2015-01-07 15.57.01.png ___ Python tracker <http://bugs.python.org/issue23187> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23187] Segmentation fault, possibly asyncio related
Ivailo Karamanolev added the comment: What I forgot to mention is that I'm using aiohttp for making lots of HTTP requests. http://bugs.python.org/issue21435 mentions asyncio and aiohttp and is somewhat memory management related so I thought I'm hitting a different manifestation of it and upgrading to 3.4.2 would fix it, but it didn't. I don't know enough about cpython to know if they are related. -- ___ Python tracker <http://bugs.python.org/issue23187> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23187] Segmentation fault, possibly asyncio related
Ivailo Karamanolev added the comment: @haypo Maybe I didn't put it prominently enough, but I upgraded to 3.4.2 by downloading the source and installing it. The same crash with the same stack trace happens. -- ___ Python tracker <http://bugs.python.org/issue23187> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23187] Segmentation fault, possibly asyncio related
Ivailo Karamanolev added the comment: > try to configure Python with ./configure --with-pydebug I'm installing 3.4.2 with this option right now and I'll reboot and run the script with gdb attached. I might be a few days before I have a result. > Are you using other external modules which are implemented in C The only module that I'm using that's implemented in C is ujson https://pypi.python.org/pypi/ujson . If you think this is relevant, I can easily try changing it to use the built-in json. > Would it be possible to share your source code I can share it privately, yes, but running it on your machine might be too complicated. Sharing the source code will probably be only useful for you to look at what libraries I am using and how I'm using asyncio. What I can do is try running it on another machine with another setup. While it is currently running on a physical machine that I set up, I can run it in parallel on a OpenVZ VPS that is installed by the VPS provider, so it should give a completely independent environment. Would that help? If yes, should I also install 3.4.2 from source with --with-pydebug? -- ___ Python tracker <http://bugs.python.org/issue23187> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23187] Segmentation fault, possibly asyncio related
Ivailo Karamanolev added the comment: @Victor It has been running for 5 days now on 3.4.2 using json instead of ujson. I want to give at least 10 days to crash and if it's still up, I plan to switch to simplejson to see how that will go, since json is quite slow. I'll keep playing with using different modules and when/if I have something significant that I can reproduce - I'll post here. If the problems are resolved, I'll close the ticket. If that doesn't sound reasonable, please let me know. -- ___ Python tracker <http://bugs.python.org/issue23187> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
