From: Goswin von Brederlow <goswin-v-b@web.de>
To: OCaml List <caml-list@inria.fr>
Subject: [Caml-list] RFH: can't figure out why my QT5 widget bindings segfault
Date: Wed, 23 Mar 2016 11:50:16 +0100 [thread overview]
Message-ID: <20160323105016.GA2235@frosties> (raw)
Hi,
I'm stuck with a bug in the Tetrix example for my QT5 bindings:
https://github.com/mrvn/ocaml-qt5
The segfault happens when you click start and the first piece is moved
one tile down in caml_mrvn_QT5_OPainter_fillRect. The arguments to the
call all look ok but something must corrupt the painter. The segfault
goes away when I force a Gc.full_major before creating a new OPainter
in TetrixBoard:148.
Any help would be welcome. I kinow it's a wild goose chase but when I
try to narrow it down to a smaller problem the segfault goes away.
MfG
Goswin
next reply other threads:[~2016-03-23 10:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 10:50 Goswin von Brederlow [this message]
2016-03-23 15:18 ` Anatoly Zaretsky
2016-03-23 17:18 ` François Bobot
2016-03-24 10:25 ` Goswin von Brederlow
2016-03-25 11:28 ` Goswin von Brederlow
2016-03-29 22:29 ` SP
2016-03-31 10:21 ` Goswin von Brederlow
2016-03-31 11:00 ` Jonas Jensen
2016-04-02 11:38 ` Goswin von Brederlow
2016-04-06 22:56 ` SP
2016-04-07 7:43 ` Goswin von Brederlow
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160323105016.GA2235@frosties \
--to=goswin-v-b@web.de \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox