VBoxTestOGL crashed with SIGSEGV in exit()

[steve]

Binary package hint: virtualbox-ose

Installed Vbox, and this message appeared upon first run...

ProblemType: Crash
Architecture: i386
Date: Thu Jan 14 17:31:06 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/lib/virtualbox/VBoxTestOGL
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20091209)
Package: virtualbox-ose 3.1.2-dfsg-1ubuntu1
ProcCmdline: /usr/lib/virtualbox/VBoxTestOGL -test 3D
ProcEnviron:
 PATH=(custom, no user)
 LANG=C
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-10.14-generic
SegvAnalysis:
 Segfault happened at: 0x6a8be8: mov (%eax),%esi
 PC (0x006a8be8) ok
 source "(%eax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: virtualbox-ose
StacktraceTop:
 ?? () from /usr/lib/nvidia-current/libGL.so.1
 ?? () from /lib/tls/i686/cmov/libc.so.6
 exit () from /lib/tls/i686/cmov/libc.so.6
 __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
Tags: lucid
Title: VBoxTestOGL crashed with SIGSEGV in exit()
Uname: Linux 2.6.32-10-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 ?? () from /usr/lib/nvidia-current/libGL.so.1
 __run_exit_handlers (status=-1215942616, listp=0x625304,
 *__GI_exit (status=0) at exit.c:100
 __libc_start_main (main=0x8049940 <main>, argc=3,
 _start ()

[Flames_in_Paradise (ellisistfroh-deactivatedaccount)]

You may wish to take a look at upstream bug

http://www.virtualbox.org/ticket/8122

http://www.virtualbox.org/wiki/Downloads (4th in row - updated Guest-additions 4.02-69551)

[Flames_in_Paradise (ellisistfroh-deactivatedaccount)]

Can't really say if this already in the Debian stack?

[Flames_in_Paradise (ellisistfroh-deactivatedaccount)]

Thank you for reporting this bug to Ubuntu. Lucid Lynx reached EOL on May,9th 2013.
See this document for currently supported Ubuntu releases:

https://wiki.ubuntu.com/Releases

We've tried recreating this bug with a current release and were unable to, given the information you've provided. Please upgrade to the latest version and re-test. If the bug is still reproducible, increase the verbosity of the steps to recreate it so we can try again.

Do feel free to report any other bugs you may find.