Lighttpd core file generated once with backtrace pointing config_parse.constprop.3()
Added by murugesh about 5 years ago
Hello All,
I have a system running linux 4.1.51 and lighttpd version 1.4.48, during startup lighttpd generated core-file that has backtrace:
(gdb) bt
#0 0x0001e55c in config_parse.constprop.3 ()
#1 0x0001f1e8 in config_parse_file_stream ()
#2 0x0001f9fc in config_parse_file ()
#3 0x00021b70 in configparser ()
#4 0x0001f05c in config_parse.constprop.3 ()
#5 0x0001f1e8 in config_parse_file_stream ()
#6 0x0001fe90 in config_read ()
#7 0x00016dc0 in server_main ()
#8 0x000162a4 in main ()
When I searched for constprop in kernel code, could see: GCC may optimize static inlines when fed constant arg(s) resulting in functions generating an associated symbol function_name.constprop.3.
In this case, function is config_parse(a static function).
With this information, how to find why lighttpd generated core file ?
Any inputs to understand root cause of this problem would be really appreciated.
Thanks,
Murugesh.
Replies (2)
RE: Lighttpd core file generated once with backtrace pointing config_parse.constprop.3() - Added by gstrauss about 5 years ago
If lighttpd is crashing when parsing the config file, it would help if you attached your config files (plus any includes) here. Then, we can try to reproduce the crash, too.
You can also try commenting out parts of your config file until the crash goes away. Please do report what is causing the crash.
If you have gdb on you system, you can run lighttpd under gdb and get more information about the crash. You did not report the system or architecture on which you are running lighttpd, so those addresses from the backtrace are not helpful. If you have an executable, you can load it in gdb and perhaps find the instruction at which it crashed.
If you can try with the latest version of lighttpd, it is possible that whatever you ran into has already been fixed since lighttpd 1.4.48 was released over a year ago.
.
However, given that this is happening at startup, and is possibly easy to reproduce, I suggest starting by comment out items from the config file until you find what triggers the crash.
RE: Lighttpd core file generated once with backtrace pointing config_parse.constprop.3() - Added by murugesh about 5 years ago
Thank you gstrauss for reply.
System architecture is Arm-64.
Lighttpd core was seen only once, trying to recreate this issue.
Thanks,
Murugesh