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

Some Help wanted with "Segmentation Fault" error and dumping core #42

Open
Hembi opened this issue Aug 27, 2018 · 6 comments
Open

Some Help wanted with "Segmentation Fault" error and dumping core #42

Hembi opened this issue Aug 27, 2018 · 6 comments
Assignees
Milestone

Comments

@Hembi
Copy link

Hembi commented Aug 27, 2018

Dear Asmodai,

I found this description: https://github.com/theAsmodai/metamod-r/wiki/Troubbleshouting
I would like to download the "Fix It All" Metamod modul by Lev, because I got on my servers Segmentation Fault error and I would like to configure and test the creating of the core dump files.
Could you please upload this module to an other file sharing site?

@s1lentq
Copy link
Collaborator

s1lentq commented Aug 28, 2018

you can use this instead "Fix It All"

#include <amxmodx>
#include <fakemeta>

public plugin_init()
{
	register_plugin("Crash", "1.0", "dev-cs.ru");

	// Generate exception code 0xC0000005
	set_task(1.0, "GenerateExceptionCode");
}

public GenerateExceptionCode()
{
	server_print("[Crash]: Executed segmentation fault! Exception code: 0xC0000005");

	// Put invalid pointer that will be generate access violation exception
	set_tr2(0xDEADBEEF, TR_InWater, true);
}

@Hembi
Copy link
Author

Hembi commented Aug 28, 2018

Thank you silentq.
The server generate the core dump and the log properly.

I would like to ask which gdb commands provide the most detailed crash log?

@theAsmodai
Copy link
Owner

backtrace

@Hembi
Copy link
Author

Hembi commented Aug 28, 2018

Hmm and this is enough? Thank you for the answer.
I have a few additional questions then please close this issue, thank you in advance for the answer.

How can this informs about the real problem?
The backtrace command prints only these information after crashing the server with the code provided by silentq:

Program terminated with signal SIGSEGV, Segmentation fault.
#0  0xf2cd1ecf in ?? () from cstrike/addons/amxmodx/modules/fakemeta_amxx_i386.so
#0  0xf2cd1ecf in ?? () from cstrike/addons/amxmodx/modules/fakemeta_amxx_i386.so
#1  0x00000000 in ?? () 

So the server throws a SIGSEGV signal which means the program tried to modified an invalid memory address and the name of the .so file which tried to write to this invalid address.
How can you figure out what exactly caused it?

@stamepicmorg
Copy link
Collaborator

stamepicmorg commented Aug 29, 2018

Hello everybody 😄

I am informing that i added at Troubbleshouting pages (rus\en)
111
mirrored links for zips from aghl forum. except of "fix it all", sorry. i will be mirror it too.. but later, if aghl up.


and @AEnimka will translate this page soon.


upd:

@Hembi, uploaded to github original fixitall plugin. link to docs already add.
fixitall_mm.0.0.zip

@Hembi
Copy link
Author

Hembi commented Sep 6, 2018

@stamepicmorg Thank you, I downloaded and used it. I am waiting for a response to my previous question.

@stamepicmorg stamepicmorg changed the title AGHL.ru died Some Help wanted with "Segmentation Fault" error and dumping core Oct 3, 2018
@stamepicmorg stamepicmorg added this to the TBD milestone Dec 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants