Browse thread
Tips to find the cause of a seg fault
[
Home
]
[ Index:
by date
|
by threads
]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: | 2010-12-01 (05:51) |
From: | Ilya Seleznev <itsuart@g...> |
Subject: | Re: [Caml-list] Tips to find the cause of a seg fault |
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