View Issue Details

IDProjectCategoryView StatusLast Update
0000785unrealircdpublic2003-05-04 20:49
Reportercomrade Assigned To 
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionopen 
Summary0000785: Does not log segmentation faults.
DescriptionWhen Unreal3.2-beta15 (only 3.2 i've tried) coredumps, I see no message from the server (I have all oper and snomask flags) and nothing is logged to ircd.log (I have it enabled in .conf for all types of logging). "core" dump is created though.
3rd party modules

Activities

codemastr

2003-03-10 00:21

reporter   ~0001843

Can you give a little more info? Such as OS?

AngryWolf

2003-03-10 14:21

reporter   ~0001847

Hmm, the same thing for me. I'm using RedHat Linux 7.1, gcc 2.95. By the way, I couldn't find anything in the code regarding to segfault logging, unlike in version 3.1.5.1 (src/ircd.c): Aieeee!!! Server terminating: Segmention fault (buf: %s)

AngryWolf

2003-03-10 14:24

reporter   ~0001848

Unreal3.2/Changes: - Removed s_segv handler
(?)

codemastr

2003-03-10 16:26

reporter   ~0001851

Well a segv is not the only way it can crash, SIGSEGV, SIGBUS, SIGFPE, etc. So it was really useless. It could still crash without letting you know.

AngryWolf

2003-03-10 19:07

reporter   ~0001857

That's ok, but with removing this even on segfault there is no warning message for ircops and no entry in the logfile...

syzop

2003-05-03 20:32

administrator   ~0002622

It's much better from a debugging point of view because the coredump contains a "memory snapshot" at the time of crash, if one would mass send a "server terminating: segmentation fault blabla" it could f*ck up stuff ;). Logging is less worse, but still... I like how it is.

codemastr

2003-05-03 23:46

reporter   ~0002625

That was the reason it was removed, it was corrupting the dumps.

Issue History

Date Modified Username Field Change
2003-05-03 20:32 syzop Note Added: 0002622
2003-05-03 23:46 codemastr Note Added: 0002625
2003-05-04 20:49 syzop Status new => closed