<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>jessenoller.com comments - Latest Comments in Does anyone know what this error is? (Segfault)</title><link>http://pyjesse.disqus.com/</link><description></description><language>en</language><lastBuildDate>Tue, 01 Jul 2008 09:14:19 -0000</lastBuildDate><item><title>Re: Does anyone know what this error is? (Segfault)</title><link>http://jessenoller.com/2008/06/30/does-anyone-know-what-this-error-is-segfault/#comment-788629</link><description>Pure python code should *never* segfault! Every segfault should be considered a bug and get fixed.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">anonymous</dc:creator><pubDate>Tue, 01 Jul 2008 09:14:19 -0000</pubDate></item><item><title>Re: Does anyone know what this error is? (Segfault)</title><link>http://jessenoller.com/2008/06/30/does-anyone-know-what-this-error-is-segfault/#comment-785199</link><description>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 ...".&lt;br&gt;&lt;br&gt;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".</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brodie Rao</dc:creator><pubDate>Mon, 30 Jun 2008 18:31:28 -0000</pubDate></item><item><title>Re: Does anyone know what this error is? (Segfault)</title><link>http://jessenoller.com/2008/06/30/does-anyone-know-what-this-error-is-segfault/#comment-784448</link><description>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. &lt;br&gt;&lt;br&gt;I think summer.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Terry Peppers</dc:creator><pubDate>Mon, 30 Jun 2008 16:47:41 -0000</pubDate></item></channel></rss>