We are running FreeRADIUS 3.0.7. FreeRADIUS has been crashing every couple days due to segmentation faults. I enabled core dumps and got a core dump from the seg fault this morning. Using the core dump, what is the best way to determine what is causing the segmentation fault? Thanks, Don
On Jun 12, 2015, at 1:13 PM, Donald Sherker <dsherker@gmail.com> wrote:
We are running FreeRADIUS 3.0.7. FreeRADIUS has been crashing every couple days due to segmentation faults. I enabled core dumps and got a core dump from the seg fault this morning. Using the core dump, what is the best way to determine what is causing the segmentation fault?
https://github.com/FreeRADIUS/freeradius-server/blob/v3.1.x/doc/bugs -Arran
https://github.com/FreeRADIUS/freeradius-server/blob/v3.1.x/doc/bugs
-Arran
I had not rebuilt the server with the --enable-developer option prior to capturing the core dump. Is there any benefit in uploading the information from the current core dump, or just rebuild the server and submit the information after another core dump happens? Thanks, Don
On Jun 12, 2015, at 1:54 PM, Donald Sherker <dsherker@gmail.com> wrote:
https://github.com/FreeRADIUS/freeradius-server/blob/v3.1.x/doc/bugs
-Arran
I had not rebuilt the server with the --enable-developer option prior to capturing the core dump. Is there any benefit in uploading the information from the current core dump, or just rebuild the server and submit the information after another core dump happens?
Rebuild. Previous core dump won't have debugging symbols. -Arran
participants (2)
-
Arran Cudbard-Bell -
Donald Sherker