From: Erik de Castro Lopo <mle+ocaml@mega-nerd.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Crashing X.Org with lablgl
Date: Mon, 26 Feb 2007 16:26:50 +1100 [thread overview]
Message-ID: <20070226162650.53f867f8.mle+ocaml@mega-nerd.com> (raw)
In-Reply-To: <20070226050151.35029.qmail@web30515.mail.mud.yahoo.com>
David Thomas wrote:
> Unfortunately, others on the project (with more clout)
> are unwilling to move these systems back to XFree86.
> While there *is* a 100% correlation between
> X.Org/XFree86 and crashing/not, it's doubtful that
> this is the only thing that's different between the
> systems.
What version of X.org? I had a lot of trouble on the Edgy Eft
release of Ubuntu which had X.org 7.0. Those troubles disappeared
when I moved to Ubuntu Feisty which has X.org 7.2.
> I guess I've a few questions.
>
> 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?
No, the xserver should not crash because of a user space
program.
> 2) Any thoughts as to how I can pinpoint the problem a
> bit better?
Try strace/ltracing the executable to pinpoint which call
to the underlying X libs are causing the crash, then write
(in C if possible) a minimal test program to recreate the
problem and send it as a bug report to the X maintainers.
If you're not up to writing the minimal C program but can
write a minimal Ocaml program I'd be happy to translate it
for you.
Hope this helps,
Erik
--
+-----------------------------------------------------------+
Erik de Castro Lopo
+-----------------------------------------------------------+
"Projects promoting programming in natural language are intrinsically
doomed to fail." -- Edsger Dijkstra
next prev parent reply other threads:[~2007-02-26 5:26 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 ` Erik de Castro Lopo [this message]
2007-02-26 5:38 ` [Caml-list] " Jacques Garrigue
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=20070226162650.53f867f8.mle+ocaml@mega-nerd.com \
--to=mle+ocaml@mega-nerd.com \
--cc=caml-list@yquem.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