Closed GoogleCodeExporter closed 9 years ago
Dear toped-supporters,
After recompiling the NVIDIA driver, the strace looks different. The strace log
file is attached. However, there is still a segmentation fault.
Best regards,
Ewald
Original comment by e...@unitybox.de
on 27 Dec 2011 at 5:25
Attachments:
It could be due to the recent changes in the openGL context.
Can you try to check-out revsion 2022 i.e. "svn update -r 2022" and rerun make.
I presume you've compiled the tool from the repository.
The other option is to configure it with --enable-debug, recompile and to rerun
it trough the gdb - it shall report exactly where it crashes.
(I can't see much from strace apart from some strange missing library messages
which most likely are not relevant. For the following week I won;t have an
access to a machine with nVidia card)
Original comment by krustev....@gmail.com
on 27 Dec 2011 at 6:00
Thanks for the hints.
Revision 2022 as well as revision 2000 showed same result.
Therefore, the assumption is that the segmentation fault is not related
directly to toped, but to the updated libraries of my linux distribution.
I will report the result of the debug run later on.
Original comment by e...@unitybox.de
on 28 Dec 2011 at 8:55
could you please post the output of
lspci -v | grep VGA
I have a machine with nVidia card which leads to the VBO type of rendering and
a stable toped:
01:00.0 VGA compatible controller: nVidian Corporation NV34 [GeForce FX Go5100]
(rev a1)
Original comment by chitlesh
on 28 Dec 2011 at 11:05
Here the requested output:
>lspci -v | grep VGA
01:00.0 VGA compatible controller: nVidia Corporation G86 [GeForce 8400M GS]
(rev a1) (prog-if 00 [VGA controller])
Original comment by e...@unitybox.de
on 28 Dec 2011 at 3:13
Latest svn version 2028 is working again after having updated glew-devel
package to latest version 1.7.0.git20111123.2145 from a different repository.
Obviously the package glew and glew-devel have been out of sync. My fault,
sorry.
Issue is closed. Thanks for your support.
Original comment by e...@unitybox.de
on 29 Dec 2011 at 2:08
No problem. Glad you've got it up&running.
Original comment by krustev....@gmail.com
on 29 Dec 2011 at 4:41
Original issue reported on code.google.com by
e...@unitybox.de
on 27 Dec 2011 at 5:09