caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jacques Garrigue <garrigue@math.nagoya-u.ac.jp>
To: david_hd@yahoo.com
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Crashing X.Org with lablgl
Date: Mon, 26 Feb 2007 14:38:59 +0900 (JST)	[thread overview]
Message-ID: <20070226.143859.41629310.garrigue@math.nagoya-u.ac.jp> (raw)
In-Reply-To: <20070226050151.35029.qmail@web30515.mail.mud.yahoo.com>

From: David Thomas <david_hd@yahoo.com>
> Working on a 3d plotting program in ocaml, using
> lablgl.  I got it working on my laptop, which is
> running Debian 3.1, with XFree86.  All seemed to run
> fine.  
> 
> Moved it over to another box, it runs fine for about a
> minute before the X server segfaults.  Duplicated the
> result on three computers at work, all running X.Org
> under Debian. Works fine on another computer running
> XFree86.

You should at least say which front-end you use for lablGL (Tcl/Tk,
Glut or LablGTK). This may be relevant.

> 1) I'm sure that there *shouldn't* be any sequence of
> calls to lablgl that should outright crash the X
> server... does anyone know how true this proves in
> practice?

Well, if there is a bug in the X server, a program may trigger it.
Personally I've never seen that for lablGL though. And the reports
I've seen were about the program itself segfaulting, not the server.

> 2) Any thoughts as to how I can pinpoint the problem a
> bit better?

Sending me the complete source to try to reproduce the problem?

You could also look at the features you are using: does turning
double-buffering off change anything, are you using lots of display
lists...

> 3) Any suggestions for working around it?  Considering
> writing a simple library implementing the parts of
> lablgl that I need (which is relatively limited, as
> it's ultimately line-drawing), but that's not
> thrilling...

It might work. But would it not be simpler to write most of your display
code in C, and just the logic in ocaml. This way, if the same problem
pops up again you would have some C code to show the developpers.

Jacques Garrigue


  parent reply	other threads:[~2007-02-26  5:39 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-26  5:01 David Thomas
2007-02-26  5:26 ` [Caml-list] " Erik de Castro Lopo
2007-02-26  5:38 ` Jacques Garrigue [this message]
2007-02-26  5:51 ` Daniel Bünzli
2007-02-26  7:29   ` Jon Harrop
2007-02-26 16:36     ` David Thomas
2007-02-26  8:01 ` Vu Ngoc San
2007-02-26 10:47   ` Jon Harrop
2007-02-26 11:23     ` Vincent Hanquez
2007-02-26 14:11       ` Jon Harrop
2007-02-26 13:41     ` Vu Ngoc San
2007-02-26 16:16       ` Conrad Hughes
2007-02-26 19:23         ` Vu Ngoc San
2007-02-26  7:07 David Thomas
     [not found] <20070226.161259.96686096.garrigue@math.nagoya-u.ac.jp>
2007-02-26  7:39 ` David Thomas
2007-02-26 11:09   ` Gerd Stolpmann
2007-02-26 16:46     ` David Thomas
2007-02-26 11:21   ` Erik de Castro Lopo
2007-02-26 17:05     ` David Thomas

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=20070226.143859.41629310.garrigue@math.nagoya-u.ac.jp \
    --to=garrigue@math.nagoya-u.ac.jp \
    --cc=caml-list@yquem.inria.fr \
    --cc=david_hd@yahoo.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).