DISQUS

DISQUS Hello! jessenoller.com comments is using DISQUS, a powerful comment system, to manage its comments. Learn more.

Community Page

jessenoller.com comments

Jump to original thread »
Author

Does anyone know what this error is? (Segfault)

Started by jnoller · 1 year ago

Ok, I’m at the end of my sanity. I’m finally over the hell-death which is hand, foot and mouth (courtesy of my daughter) which means I can type again, and now I’m stuck trying to debug some dastardly segfault. Here is it (courtesy of /var/log/messages):
Jun 30 12:49:13 NON kernel: python[29965]: segfault at 000000010000000f rip

000000000044068e rsp [...] ... Continue reading »

3 comments

  • Terry Peppers

    1 year ago

    Jesse, I'm not sure which I loathe more from my son. The winter set of colds, flus and viruses. Or the summer set of rashes, flus and viruses - of the gastrointestinal variation.

    I think summer.
    reply
  • Brodie Rao

    1 year ago

    Were you not able to run gdb? You can usually use it to get the stack trace of a segfault (using bt/backtrace). You have to load the Python binary with it though (and not your script), and then use "run /path/to/your/script arg1 arg2 ...".

    You can also change the user limit on core dumps so a full dump is produced on a segfault using "ulimit -c unlimited", and then load that core dump into gdb with "core core.123456".
    reply
  • anonymous

    1 year ago

    Pure python code should *never* segfault! Every segfault should be considered a bug and get fixed.
    reply

Add New Comment

Returning? Login