From: oliver@first.in-berlin.de
To: 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:57 +0100 [thread overview]
Message-ID: <20101201105157.GC2196@siouxsie> (raw)
In-Reply-To: <AANLkTi=xyXhsdqmypbTLniJhDOCMHMbYMONHM8uuyfyr@mail.gmail.com>
On Wed, Dec 01, 2010 at 11:26:19AM +0100, Philippe Veber wrote:
> 2010/12/1 <oliver@first.in-berlin.de>
>
> > Hi,
> >
> >
> > On Wed, Dec 01, 2010 at 09:32:16AM +0100, Philippe Veber wrote:
> > > Actually I was not confident I could extract a small program reproducing
> > the
> > > issue until ... you had me try ! I could get a very tiny example that
> > > behaves exactly the same, which does not involve opengl at all, only sdl.
> > > Here it is :
> > [...]
> >
> >
> > After installing some sdl-related packages, I could comopile the code.
> > So far it does not crash.
> >
> > What actions do create the segfault for you?
> >
>
> roll the mouse wheel up or down fast with the cursor on the window. However,
> I know that this problem does not occur everywhere, so you might well
> observe nothing ...
[...]
No crash happened.
Normally I'm very gifted to crash software.... by just looking at it.
If there is a bug, it will find me ;)
Did you tried another X-driver?
In your valgrind printout there was mentioned "libnvidia".
And a crash seems to have been occured at that part:
> ==11306== by 0x4215D5: camlHum__entry (in
> /home/pveber/hum/_build/src/hum.native)
> ==11306== by 0xC5767A7: ???
> ==11306==
> ==11306== Conditional jump or move depends on uninitialised value(s)
> ==11306== at 0x7695580: ??? (in
> /usr/lib/nvidia-current/libnvidia-glcore.so.260.19.06)
> ==11306== by 0x1000000000000: ???
> ==11306==
> vex amd64->IR: unhandled instruction bytes: 0xFF 0xD8 0xC 0xF9 0xFF 0xD8
> ==11306== valgrind: Unrecognised instruction at address 0x4992cb.
> ==11306== Your program just tried to execute an instruction that Valgrind
So, please chack this. Maybe one of the free drivers does work better,
or maybe an update could help.
If you update your kernel, then you might also need to update the
X-drivers, because the nvidia stuff is non-free binary stuff,
and maybe some bindings don't work correctly with a new kernel.
I once experienced problems the other way around: crashing blender
with the free drivers, just by scaling into a view more and more,
and no crash with the non-free drivers.
This X11-driver part is really a desert...
...and even if you don't use OpenGL commands... the driver that you installed
and configured will be used nevretheless, and if there is something wrong, you
will get your crashes.
Look if the X11-driver-bindings are all up to date for the driver you use now,
and also try another X11-driver...
Ciao,
Oliver
next prev parent reply other threads:[~2010-12-01 10: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 [this message]
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
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=20101201105157.GC2196@siouxsie \
--to=oliver@first.in-berlin.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;
as well as URLs for NNTP newsgroup(s).