We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Witam mam taki błąd. Oto report z crashu:
MTA:SA Server v1.3.3-r5610-release crash report. Caught 10 addresses ...
Backtrace: #0 - ./core.so(_ZN13CCrashHandler21HandleExceptionGlobalEi+0x69) [0xf74c62d9] #1 - [0xf77c5400] #2 - /lib32/libncursesw.so.5(_nc_printf_string+0x33) [0xf748d853] #3 - /lib32/libncursesw.so.5(vwprintw+0x24) [0xf7488a74] #4 - /lib32/libncursesw.so.5(printw+0x30) [0xf7488bd0] #5 - ./core.so(_ZN11CServerImpl3RunEiPPc+0x6ac) [0xf74c8bec] #6 - ./core.so(Run+0x46) [0xf74df3f6] #7 - ./mta-server(__gxx_personality_v0+0x4df) [0x8048d43] #8 - /lib32/libc.so.6(__libc_start_main+0xe6) [0xf752dca6] #9 - ./mta-server(__gxx_personality_v0+0x4d) [0x80488b1]
The text was updated successfully, but these errors were encountered:
Zgłoś to na http://bugs.mtasa.com/ Najlepiej jakbyś spakował cały serwer (binarki + zasoby) i tam udostępnił. Ewentualnie możesz zrobić to tu.
Sorry, something went wrong.
No branches or pull requests
Witam mam taki błąd. Oto report z crashu:
MTA:SA Server v1.3.3-r5610-release crash report.
Caught 10 addresses ...
Backtrace:
#0 - ./core.so(_ZN13CCrashHandler21HandleExceptionGlobalEi+0x69) [0xf74c62d9]
#1 - [0xf77c5400]
#2 - /lib32/libncursesw.so.5(_nc_printf_string+0x33) [0xf748d853]
#3 - /lib32/libncursesw.so.5(vwprintw+0x24) [0xf7488a74]
#4 - /lib32/libncursesw.so.5(printw+0x30) [0xf7488bd0]
#5 - ./core.so(_ZN11CServerImpl3RunEiPPc+0x6ac) [0xf74c8bec]
#6 - ./core.so(Run+0x46) [0xf74df3f6]
#7 - ./mta-server(__gxx_personality_v0+0x4df) [0x8048d43]
#8 - /lib32/libc.so.6(__libc_start_main+0xe6) [0xf752dca6]
#9 - ./mta-server(__gxx_personality_v0+0x4d) [0x80488b1]
The text was updated successfully, but these errors were encountered: