[PyQt] Slot type validation: int/qint64

[Florian Bruhin]

* VA <dev+pyqt at indigo.re> [2016-04-30 16:18:37 +0200]:
> I'm using Qscintilla. With PyQt 5.5, I could successfully connect:
> - SCN_MODIFIED (int, int, const char *, int, int, int, int, int, int,
> int) to @Slot(int, int, str, int, int, int, int, int, int, int)
> - SCN_MACRORECORD (unsigned int, unsigned long, void *) to @Slot(int,
> int, object)
> Now, not only slot validation prevents it from working, but if I repeat
> the C++ signature (quoting the type names), it may work but after a few
> signal emissions and the slot getting called a few times, Python segfaults.
> If I completely omit the @Slot decorator, the connection works too, but
> it still quickly segfaults after a few emissions.
> Even if I'm not doing anything with the slots arguments (the slot just
> containing "pass"), it still segfaults.
> What could cause those segfaults?

Can you show a stacktrace? On Linux you can simply prepend catchsegv
to your commandline to get one.

Maybe QScintilla emits NULL/None for the const char* and you're
running into this?

https://www.riverbankcomputing.com/pipermail/pyqt/2016-April/037375.html

Florian

-- 
http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
         I love long mails! | http://email.is-not-s.ms/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <https://www.riverbankcomputing.com/pipermail/pyqt/attachments/20160430/cc952753/attachment.sig>