Could you try the steps at http://stackoverflow.com/a/11369475/2097780? They
allow you to get a better idea of where libc is crashing.
Cyd Haselton wrote:
>Managed to get this out of logcat:
>F(11914) Fatal signal 11 (SIGSEGV) at 0x (code=1), thread
>11914 (python) (libc)
>
>[ 01-29 19:
Managed to get this out of logcat:
F(11914) Fatal signal 11 (SIGSEGV) at 0x (code=1), thread
11914 (python) (libc)
[ 01-29 19:30:55.855 23373:23373 F/libc ]
Fatal signal 11 (SIGSEGV) at 0x (code=1), thread 23373 (python)
Less detail than strace but it seems to be that python
Hello,
As BDFL-delegate, I'd like to pronounce soon on PEP 475 - "Retry system
calls failing with EINTR". I've just pushed some small rephrasings,
which should appear soon (at https://www.python.org/dev/peps/pep-0475/).
There is a working implementation by Charles-François at
http://bugs.python.
Found a patch for at bugs.python.org addressing a segfault issue for
android but even afternapplying it i'm still getting a segfault.
I ran a strace with the verbose option and am attaching it to this
update. If not helpful, I'll see if I can hook up the debugging
bridge to the tablet but as ment
Hi!
Finally, here are the results:
http://blog.frite-camembert.net/python-survey-2014.html
Here is the auto-generated Google Forms recap:
https://docs.google.com/forms/d/1DqxkNi4GvyTCu54usSdE1DjW29zw1tc52iMeH3z4heg/viewanalytics
(more elegant than my matplotlib graphs - I'd have no future as a
desi
On 29 January 2015 at 04:53, Andrea Griffini wrote:
> The names stored in op_names are totally unrelated as they can be attribute
> names, module names, global names; you basically don't know much about them
> unless you also inspect the actual bytecode using them (and the same name
> can be used
