crash - Signal 11 on entering map

If you've had any problems with Nexuiz, or would like to report bugs, post here.

Moderators: Nexuiz Moderators, Moderators

Postby esteel » Tue Jun 20, 2006 8:30 am

divVerent wrote:Still we NEED more information on the problem. I can provide a debug build, but please test it then.

Of course. Seems mana is happy to help ;) Thanks!
Last edited by esteel on Thu Aug 31, 2006 8:44 pm, edited 1 time in total.
esteel
Site admin and forum addon
 
Posts: 3924
Joined: Wed Mar 01, 2006 8:27 am

Postby mana » Tue Jun 20, 2006 8:36 am

Of course :) i am happy with bug reports being recognized. But i can start testing any builds in 8 hours earliest. If you don't want to make the builds available in public, just send me the links: mana@cyor.de.

If communication via ICQ helps, you can contact me: 27495311

but i will have a look at the bord as well.

until then
greets
Mana
mana
Member
 
Posts: 14
Joined: Sat Jun 17, 2006 1:55 pm

Postby divVerent » Tue Jun 20, 2006 7:03 pm

mana wrote:Of course :) i am happy with bug reports being recognized. But i can start testing any builds in 8 hours earliest. If you don't want to make the builds available in public, just send me the links: mana@cyor.de.

If communication via ICQ helps, you can contact me: 27495311

but i will have a look at the bord as well.


Okay, can you try the builds here: http://mensa.ath.cx/~polzer/temp/dpdebug.zip

Put the files from this zip file in your Nexuiz installation folder.

If you still get the crash, try doing this on a shell:

Code: Select all
$ ulimit -Sc  unlimited
$ ./nexuiz-glx


When it crashes again, you will get a "core" file. Assuming it will be called core.7131 (the number can vary), you then do the following:

Code: Select all
$ gdb nexuiz-glx core.7131
(gdb) bt


and post the output of that. This should help us.

Thanks!
1. Open Notepad
2. Paste: ÿþMSMSMS
3. Save
4. Open the file in Notepad again

You can vary the number of "MS", so you can clearly see it's MS which is causing it.
divVerent
Site admin and keyboard killer
 
Posts: 3809
Joined: Thu Mar 02, 2006 4:46 pm
Location: BRLOGENSHFEGLE

Postby mana » Tue Jun 20, 2006 7:42 pm

here the results

nexuiz-glx:
Same crash as my first post

nexuiz-glx after the ulimit-command:
no crash, but i get droped out of the map (that i do not see) and the main screen with the menu is presented. The Mouse pointer is very slow then, the interfaces reacts slowly, so i exit nexuiz via the quit button. There is no core.* File created that i can see.
mana
Member
 
Posts: 14
Joined: Sat Jun 17, 2006 1:55 pm

Postby mana » Tue Jun 20, 2006 7:50 pm

now _very strange_:
i do the debug in a screen like you told me above. I am in the nexuiz directory where i unziped the nexuiz-glx, the timestamps show that it must be the right executable. I issue

    gdb nexuiz-glx
    (gdb) run -nexuiz


I try to join a game like all the attempts before, and suddenly i am in. I can play with poor performance, i guess because of gdb .. no crash ...

i leave it to you to interpret this :)

greets
Mana
mana
Member
 
Posts: 14
Joined: Sat Jun 17, 2006 1:55 pm

Postby mana » Tue Jun 20, 2006 8:09 pm

I wanted to run my self-compiled binary now without gdb, but it keeps complaining about not beeing able to open files in data-dir. The binary is in nexuiz main folder, i tried to set -basedir /path/to/nexuiz. Running the selfcompiled binary in gdb does not work anymore too. Maybe the ulimit or something else messed up my environment? Using another console doesn't help. Reboot?

you debug-binary does not have this problem.
mana
Member
 
Posts: 14
Joined: Sat Jun 17, 2006 1:55 pm

Postby divVerent » Tue Jun 20, 2006 9:19 pm

No idea what that could be, can you try starting it from the console?

Does my binary work fine or can you reproduce the crash with it?
1. Open Notepad
2. Paste: ÿþMSMSMS
3. Save
4. Open the file in Notepad again

You can vary the number of "MS", so you can clearly see it's MS which is causing it.
divVerent
Site admin and keyboard killer
 
Posts: 3809
Joined: Thu Mar 02, 2006 4:46 pm
Location: BRLOGENSHFEGLE

Postby Comp_Lex » Tue Jun 20, 2006 10:27 pm

Hello, i'm trying to make cl-debug, but i can't compile it. This is what i get:

Code: Select all
make bin-debug \
                DP_MAKE_TARGET=linux DP_SOUND_API=ALSA \
                EXE="darkplaces-glx" LDFLAGS_COMMON="-lm -ldl -L/usr/X11R6/lib64 -lX11 -lXext -lXxf86dga -lXxf86vm -lasound"
make[1]: Map '/home/alexander/Nexuiz/Nexuiz/sources/darkplaces' wordt binnengegaan

========== darkplaces-glx (debug) ==========
make darkplaces-glx \
                DP_MAKE_TARGET=linux DP_SOUND_API=ALSA \
                CFLAGS="-MD -Wall -Wsign-compare  -ggdb "\
                LDFLAGS="-g -ggdb  -lm -ldl -L/usr/X11R6/lib64 -lX11 -lXext -lXxf86dga -lXxf86vm -lasound"
make[2]: Map '/home/alexander/Nexuiz/Nexuiz/sources/darkplaces' wordt binnengegaan
gcc -MD -Wall -Wsign-compare  -ggdb  -c vid_glx.c -o vid_glx.o -I/usr/X11R6/include
vid_glx.c:33:36: fout: X11/extensions/xf86dga.h: Onbekend bestand of map
vid_glx.c:35:38: fout: X11/extensions/xf86vmode.h: Onbekend bestand of map
vid_glx.c:105: fout: syntax error before ‘init_vidmode’
vid_glx.c:105: let op: type krijgt standaardwaarde ‘int’ in de declaratie van ‘init_vidmode’
vid_glx.c:105: let op: datadefinitie heeft geen type of opslagklasse
vid_glx.c: In functie ‘IN_Activate’:
vid_glx.c:273: let op: impliciete declaratie van functie ‘XF86DGAQueryVersion’
vid_glx.c:282: let op: impliciete declaratie van functie ‘XF86DGADirectVideo’
vid_glx.c:282: fout: ‘XF86DGADirectMouse’ is hier niet gedeclareerd (eerste gebruik in deze functie)
vid_glx.c:282: fout: (Elke niet-gedeclareerde naam wordt slechts één
vid_glx.c:282: fout: keer vermeld voor elke functie waarin hij staat.)
vid_glx.c: In functie ‘VID_Shutdown’:
vid_glx.c:520: let op: impliciete declaratie van functie ‘XF86VidModeSwitchToMode’
vid_glx.c: In functie ‘VID_SetGamma’:
vid_glx.c:595: let op: impliciete declaratie van functie ‘XF86VidModeSetGammaRamp’
vid_glx.c: In functie ‘VID_GetGamma’:
vid_glx.c:600: let op: impliciete declaratie van functie ‘XF86VidModeGetGammaRamp’
vid_glx.c: In functie ‘VID_InitMode’:
vid_glx.c:671: let op: impliciete declaratie van functie ‘XF86VidModeQueryVersion’
vid_glx.c:705: fout: ‘XF86VidModeModeLine’ is hier niet gedeclareerd (eerste gebruik in deze functie)
vid_glx.c:705: fout: ‘current_vidmode’ is hier niet gedeclareerd (eerste gebruik in deze functie)
vid_glx.c:706: fout: ‘XF86VidModeModeInfo’ is hier niet gedeclareerd (eerste gebruik in deze functie)
vid_glx.c:706: fout: ‘vidmodes’ is hier niet gedeclareerd (eerste gebruik in deze functie)
vid_glx.c:710: fout: syntax error before ‘)’ token
vid_glx.c:710: fout: request for member ‘dotclock’ in something not a structure or union
vid_glx.c:711: let op: impliciete declaratie van functie ‘XF86VidModeGetModeLine’
vid_glx.c:711: fout: request for member ‘dotclock’ in something not a structure or union
vid_glx.c:713: let op: impliciete declaratie van functie ‘XF86VidModeGetAllModeLines’
vid_glx.c:745: let op: impliciete declaratie van functie ‘XF86VidModeSetViewPort’
vid_glx.c:837: let op: impliciete declaratie van functie ‘XF86VidModeGetGammaRampSize’
make[2]: *** [vid_glx.o] Fout 1
make[2]: Map '/home/alexander/Nexuiz/Nexuiz/sources/darkplaces' wordt verlaten
make[1]: *** [bin-debug] Fout 2
make[1]: Map '/home/alexander/Nexuiz/Nexuiz/sources/darkplaces' wordt verlaten
make: *** [cl-debug] Fout 2


"Fout" = Error
"Let op" = Warning

BTW, I'm using Ubuntu 6.06.
Comp_Lex
Newbie
 
Posts: 6
Joined: Mon Jun 19, 2006 11:45 am

Postby mana » Tue Jun 20, 2006 10:39 pm

divVerent, i did everything from the console so far :)

and again, yes your binary crashes also but only when _not_ started with gdb and without the ulimit thing. see above.
mana
Member
 
Posts: 14
Joined: Sat Jun 17, 2006 1:55 pm

Postby divVerent » Tue Jun 20, 2006 10:43 pm

Comp_Lex wrote:Hello, i'm trying to make cl-debug, but i can't compile it. This is what i get:

Code: Select all
make bin-debug \
                DP_MAKE_TARGET=linux DP_SOUND_API=ALSA \
                EXE="darkplaces-glx" LDFLAGS_COMMON="-lm -ldl -L/usr/X11R6/lib64 -lX11 -lXext -lXxf86dga -lXxf86vm -lasound"
make[1]: Map '/home/alexander/Nexuiz/Nexuiz/sources/darkplaces' wordt binnengegaan

========== darkplaces-glx (debug) ==========
make darkplaces-glx \
                DP_MAKE_TARGET=linux DP_SOUND_API=ALSA \
                CFLAGS="-MD -Wall -Wsign-compare  -ggdb "\
                LDFLAGS="-g -ggdb  -lm -ldl -L/usr/X11R6/lib64 -lX11 -lXext -lXxf86dga -lXxf86vm -lasound"
make[2]: Map '/home/alexander/Nexuiz/Nexuiz/sources/darkplaces' wordt binnengegaan
gcc -MD -Wall -Wsign-compare  -ggdb  -c vid_glx.c -o vid_glx.o -I/usr/X11R6/include
vid_glx.c:33:36: fout: X11/extensions/xf86dga.h: Onbekend bestand of map
vid_glx.c:35:38: fout: X11/extensions/xf86vmode.h: Onbekend bestand of map
vid_glx.c:105: fout: syntax error before ‘init_vidmode’
vid_glx.c:105: let op: type krijgt standaardwaarde ‘int’ in de declaratie van ‘init_vidmode’


Sorry, I don't speak Dutch, but I guess this means that X11/extensions/xf86dga.h is missing. If Ubuntu is anything like Debian, you have to install a package named x11proto-xf86vidmode-dev (that's what it is called in Debian unstable) or xlibs-static-dev (the package in Debian stable). No idea where a packages.debian.org equivalent for Ubuntu is, but maybe this already helps you.
1. Open Notepad
2. Paste: ÿþMSMSMS
3. Save
4. Open the file in Notepad again

You can vary the number of "MS", so you can clearly see it's MS which is causing it.
divVerent
Site admin and keyboard killer
 
Posts: 3809
Joined: Thu Mar 02, 2006 4:46 pm
Location: BRLOGENSHFEGLE

PreviousNext

Return to Nexuiz - Support / Bugs

Who is online

Users browsing this forum: No registered users and 1 guest

cron