Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Segfault when running godot-tools on LXLE (Linux) #2067

Closed
And-0 opened this issue Jun 10, 2015 · 2 comments
Closed

Segfault when running godot-tools on LXLE (Linux) #2067

And-0 opened this issue Jun 10, 2015 · 2 comments
Labels

Comments

@And-0
Copy link

And-0 commented Jun 10, 2015

Whenever I try running godot-tools on my netbook running LXLE I get a segfault error. (LXLE is based on Ubuntu/Lubuntu's LTS version, currently 14.04.) GDB backtrace follows:

(gdb) run
Starting program: /home/ando/Downloads/godot_x11-1.1stable.64
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
warning: the debug information found in "/usr/lib/x86_64-linux-gnu/dri/radeon_dri.so" does not match "/usr/lib/x86_64-linux-gnu/dri/i915_dri.so" (CRC mismatch).

[New Thread 0x7fffe9b66700 (LWP 7574)]
[New Thread 0x7fffe9365700 (LWP 7575)]
[New Thread 0x7fffe92f8700 (LWP 7576)]

Program received signal SIGSEGV, Segmentation fault.
0x0000000000000000 in ?? ()
(gdb) bt
#0 0x0000000000000000 in ?? ()
#1 0x0000000000502e03 in RasterizerGLES2::init() ()
#2 0x0000000000f6c3c0 in VisualServerRaster::init() ()
#3 0x0000000000f2c0e0 in VisualServerWrapMT::init() ()
#4 0x0000000000413f3e in OS_X11::initialize(OS::VideoMode const&, int, int) ()
#5 0x0000000000416e7e in Main::setup2() ()
#6 0x0000000000418ebd in Main::setup(char const_, int, char_*, bool) ()
#7 0x000000000040ef7a in main ()

UPDATE:
I tried running godot-tools on a live setup of Manjaro (based on Arch Linux) on the same netbook, and the game worked. I guess the problem lies with my setup then, not with Godot.

@bojidar-bg
Copy link
Contributor

To me it seems like the GLES2 rasterizer doesn't work properly.. Maybe some GPU driver problem?

@punto-
Copy link
Contributor

punto- commented Jun 13, 2015

Yeah, it looks like a driver issue. Whatever function from gl that is being
called on RasterizerGLES2::init() is not available, so it's a null pointer,
that's why the top frame is null.

On Sat, Jun 13, 2015 at 5:41 AM, Bojidar Marinov notifications@github.com
wrote:

To me it seems like the GLES2 rasterizer doesn't work properly.. Maybe
some GPU driver problem?


Reply to this email directly or view it on GitHub
#2067 (comment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants