From: Ilya Seleznev <itsuart@gmail.com>
To: Philippe Veber <philippe.veber@googlemail.com>
Cc: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] Tips to find the cause of a seg fault
Date: Wed, 1 Dec 2010 11:51:43 +0600 [thread overview]
Message-ID: <AANLkTi=ihJxSNoEC0yq-3g36Ls-62V=WC8YaymZ2u3Gs@mail.gmail.com> (raw)
In-Reply-To: <AANLkTik4n=XgNhA6SsQXV_ZvQSsPrQFFYjPQaqSNnYKn@mail.gmail.com>
On Wed, Dec 1, 2010 at 5:08 AM, Philippe Veber
<philippe.veber@googlemail.com> wrote:
> Short story (details below): I'm currently writing a program relying on
> react, lablgl and ocamlsdl. This program segfaults on my laptop under two
> linux distributions (ubuntu and gentoo) but doesn't on a PC under ubuntu.
> The seg fault occurs with both bytecode and native executables. I don't do
> any marshaling nor use any typing magic; stack overflow is not likely. I
> humbly ask this list about means to improve valgrind or gdb outputs, which
> don't report informative function names, or more generally, any tip that
> could help me to locate the origin of the problem.
I would log mouse events, that went into 'picking_handler' to ensure
that no unexpected input sent by SDL.
--
With best regards,
Ilya Seleznev
next prev parent reply other threads:[~2010-12-01 5:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-30 23:08 Philippe Veber
2010-11-30 23:18 ` [Caml-list] " oliver
2010-12-01 8:32 ` Philippe Veber
2010-12-01 9:15 ` oliver
2010-12-01 10:26 ` Philippe Veber
2010-12-01 10:51 ` oliver
2010-12-01 15:08 ` Philippe Veber
2010-12-01 1:59 ` Romain Beauxis
2010-12-01 15:17 ` Philippe Veber
2010-12-01 15:27 ` oliver
2010-12-01 16:15 ` Romain Beauxis
2010-12-01 5:51 ` Ilya Seleznev [this message]
2010-12-01 15:21 ` Philippe Veber
[not found] <1182061596.483210.1291158525016.JavaMail.root@zmbs1.inria.fr>
2010-12-03 15:43 ` Damien Doligez
2010-12-05 14:50 ` Philippe Veber
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='AANLkTi=ihJxSNoEC0yq-3g36Ls-62V=WC8YaymZ2u3Gs@mail.gmail.com' \
--to=itsuart@gmail.com \
--cc=caml-list@inria.fr \
--cc=philippe.veber@googlemail.com \
/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;
as well as URLs for NNTP newsgroup(s).