<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>I don't have any clue as to why the segfault could be popping up,
but it would probably help you to generate a core dump and analyze
it with gdb. You can do that with the following steps (note you'll
need to have python compiled in debug):</p>
<p>1. Enable core dumps with "ulimit -c unlimited"</p>
<p>2. Get your program to crash</p>
<p>3. Open the core dump with gdb "gdb python core"</p>
<p>4. Use the python gdb extensions to analyze where the segfault is
happening in the python code (see
<a class="moz-txt-link-freetext" href="https://wiki.python.org/moin/DebuggingWithGdb">https://wiki.python.org/moin/DebuggingWithGdb</a>)</p>
<br>
<div class="moz-cite-prefix">On 09/06/2016 07:56 AM, Xavion wrote:<br>
</div>
<blockquote
cite="mid:CAKnx8Y7jnszA_TAjXkdEDNuBn+VYZ5RUGkbah2x2J3UnfNYpBw@mail.gmail.com"
type="cite">
<div dir="ltr">Hi All,
<div><br>
</div>
<div>I've just finished converting my PyQt4 application to
PyQt5, and I keep seeing the following error message whenever
I <u>exit</u> it:</div>
<blockquote style="margin:0px 0px 0px
40px;border:none;padding:0px">
<div>fish: “./App.pyw” terminated by signal SIGSEGV (Address
boundary error)</div>
</blockquote>
<br>
<div>This doesn't happen with the PyQt4 edition of the program,
so I'm guessing it's either due to a bug in Qt5 or PyQt5.</div>
<div><br>
</div>
<div>When I run the program via GDB, I get the following
output. The backtrace is available in the first attachment.</div>
<blockquote style="margin:0 0 0 40px;border:none;padding:0px">Thread
1 "python" received signal SIGSEGV, Segmentation
fault.0x00007ffff5cf3643 in ?? () from
/usr/lib/libQt5Core.so.5<br>
</blockquote>
<br>
<div>It appeared to be related to the 'Breeze' style, so I
installed <a moz-do-not-send="true"
href="https://sourceforge.net/projects/qt5ct/">qt5ct</a> and
switched to 'Fusion'. When I then ran my program (again via
GDB), the output and backtrace were entirely different.</div>
<div>
<blockquote style="margin:0px 0px 0px
40px;border:none;padding:0px">
<div>
<div>Thread 2 "Qt bearer threa" received signal SIGSEGV,
Segmentation fault.</div>
<div>[Switching to Thread 0x7fffea52b700 (LWP 22844)]</div>
<div>0x00007fffe98cbbe5 in
QDBusMetaType::typeToSignature(int) () from
/usr/lib/libQt5DBus.so.5</div>
</div>
</blockquote>
</div>
<div><br>
</div>
<div>I'm on Arch Linux, by the way. I'm using Python
v3.5.2-1, Qt v5.7.0-2, and PyQt v5.7-2. All are packages
installed from the [extra] repository.</div>
<div><br>
</div>
<div>With all of this in mind, is anyone able to pinpoint the
nature of the problem(s)? If so, is it the sort of thing
that'd be easy enough to fix in time for the next (Py)Qt5
release?</div>
<div><br clear="all">
<div><br>
</div>
-- <br>
<div class="gmail_signature">
<div><span style="color:rgb(68,68,68)"><font size="2">Regards,
Xavion.<br>
<br>
</font></span></div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
PyQt mailing list <a class="moz-txt-link-abbreviated" href="mailto:PyQt@riverbankcomputing.com">PyQt@riverbankcomputing.com</a>
<a class="moz-txt-link-freetext" href="https://www.riverbankcomputing.com/mailman/listinfo/pyqt">https://www.riverbankcomputing.com/mailman/listinfo/pyqt</a></pre>
</blockquote>
<br>
</body>
</html>