[Linux] Crash when changing from fullscreen to windowed mode

Bugs that have been resolved.

Moderator: Graf Zahl

Locked
User avatar
Daniele C.
Posts: 54
Joined: Sun Oct 21, 2007 23:24
Location: Roma

[Linux] Crash when changing from fullscreen to windowed mode

Post by Daniele C. »

This crash happened while changing from fullscreen to windowed mode, no leves was yet loaded.
Attachments
zdoom-crash.zip
(2.18 KiB) Downloaded 68 times
User avatar
Graf Zahl
GZDoom Developer
GZDoom Developer
Posts: 7148
Joined: Wed Jul 20, 2005 9:48
Location: Germany
Contact:

Post by Graf Zahl »

This goes the quick way to the trash because there's nothing in here that would help me to investigate the problem.

I can't gather any information from the crash log as it is specific to your machine.
User avatar
Daniele C.
Posts: 54
Joined: Sun Oct 21, 2007 23:24
Location: Roma

Post by Daniele C. »

It happens even after loading a level or after switching from fullscreen to windowed mode.

Problem is that I can only switch fullscreen/windowed editing the zdoom.ini.

Please do not say "this goes directly to the trash can", if you want to support GZDoom for linux. My raw sensation is that you are supporting GZDoom for linux, but don't really like doing it.

A more open reply would have been "this does not tell me anything, please do this and this"...

I have developed for both Win32 and Linux, I will now see what debugging informations I can get through gdb

Thank you
User avatar
Daniele C.
Posts: 54
Joined: Sun Oct 21, 2007 23:24
Location: Roma

Post by Daniele C. »

Graf Zahl wrote:This goes the quick way to the trash because there's nothing in here that would help me to investigate the problem.

I can't gather any information from the crash log as it is specific to your machine.
OK, so why does GZdoom (ZDoom?) generate this if it is useless to you? It's not a real question, but a rethorical question: I submitted it because I thought it could be useful someway.

I will submit a stacktrace instead.
User avatar
Graf Zahl
GZDoom Developer
GZDoom Developer
Posts: 7148
Joined: Wed Jul 20, 2005 9:48
Location: Germany
Contact:

Post by Graf Zahl »

This only of use to the person who built the executable. If you re-do this with a debug build I'd get some usable information.
User avatar
Daniele C.
Posts: 54
Joined: Sun Oct 21, 2007 23:24
Location: Roma

Post by Daniele C. »

I have found a similar topic:

http://skulltag.com/forum/viewtopic.php?f=49&t=10716

The solution seems to be here:

http://forum.zdoom.org/viewtopic.php?f=7&t=14764

I will post again when I find a patch or something

Thanks
User avatar
Daniele C.
Posts: 54
Joined: Sun Oct 21, 2007 23:24
Location: Roma

Crash in libGL

Post by Daniele C. »

I have libFLAC v1.2.1-r1, but my crash does not seem to be there.

I have used GDB and got this backtrace:

Code: Select all

#0  0xb3b54490 in ?? ()
No symbol table info available.
#1  0xb760e749 in __glXInitialize ()
   from //usr//lib/opengl/xorg-x11/lib/libGL.so.1
No symbol table info available.
#2  0xb760a14d in ?? () from //usr//lib/opengl/xorg-x11/lib/libGL.so.1
No symbol table info available.
#3  0x0891a1b0 in ?? ()
No symbol table info available.
#4  0x00000002 in ?? ()
No symbol table info available.
#5  0xb764eff4 in ?? () from //usr//lib/opengl/xorg-x11/lib/libGL.so.1
No symbol table info available.
#6  0x085b5bc0 in ?? ()
No symbol table info available.
#7  0x00000000 in ?? ()
No symbol table info available.
I have Mesa v6.5.2-r1 (libGL provider), I will investigate a bit more about this library vs GZdoom.

Edit: I have added the same crash log generated with gzdoomd (built with 'make DEBUG=1'). It does not seem to contain more useful informations, to me. I am still recompiling Mesa with debug symbols so that I can better isolate the crash in libGL.so.
Attachments
zdoom-crash-debug.zip
zdoom-crash.log created with gzdoomd
(2.18 KiB) Downloaded 65 times
User avatar
Graf Zahl
GZDoom Developer
GZDoom Developer
Posts: 7148
Joined: Wed Jul 20, 2005 9:48
Location: Germany
Contact:

Post by Graf Zahl »

That backtrace looks like somewhere in libgl some invalid code is called. I'm afraid that if that is true I don't think I can do much about it.
User avatar
Daniele C.
Posts: 54
Joined: Sun Oct 21, 2007 23:24
Location: Roma

Post by Daniele C. »

Yes, but why the zdoom-crash.log talks about libpixbufloader-png.so?

I am confused, is it in libGL.so or in libpixbufloader-png.so, in your opinion?

I have generated the crash again with gdb and mesa compiled with debug flag, but the backtrace did not tell anything more...weird.
User avatar
Graf Zahl
GZDoom Developer
GZDoom Developer
Posts: 7148
Joined: Wed Jul 20, 2005 9:48
Location: Germany
Contact:

Post by Graf Zahl »

No idea what libpixbufloader is. Apparently something that is called internally. Have you had success starting any other GL application?
User avatar
Daniele C.
Posts: 54
Joined: Sun Oct 21, 2007 23:24
Location: Roma

Post by Daniele C. »

Graf Zahl wrote:No idea what libpixbufloader is.
I think it might be the GTK function (loader) used by GZDoom to repaint the menu graphics, for example.
Graf Zahl wrote: Apparently something that is called internally. Have you had success starting any other GL application?
ALL GL applications start successfully, also GZDoom and I can play and everything else. This crash only happens when switching from fullscreen to windowed (and viceversa).

Also, I have DRI enabled
Locked

Return to “Closed Bugs”