Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Bugs in rlm_perl config {} section handling #1675
Comments
|
It took me some time to reproduce this: on my build the
Of course the line numbers don't match with any In unrelated news: found this in the Perl source:
eeeeeeeeee? |
|
Btw: I've added some debugging stuff in |
|
any progress on this? I tend not to work on rlm_perl due to religious objections :) |
|
Not really, the hash looks perfectly fine in freeradius context before we try to free it, so I guess it's some incorrect usage of the Perl internals. |
herwinw
pushed a commit
to herwinw/freeradius-server
that referenced
this issue
Aug 22, 2016
|
|
79a5406
|
herwinw
referenced
this issue
Aug 22, 2016
Merged
Free rad_perlconf_hv in correct perl context #1681
herwinw
pushed a commit
to herwinw/freeradius-server
that referenced
this issue
Aug 22, 2016
|
|
ef56000
|
arr2036
closed this
in #1681
Aug 23, 2016
arr2036
added a commit
that referenced
this issue
Aug 23, 2016
|
|
+ arr2036 |
77d2ace
|
alandekok
added a commit
that referenced
this issue
Aug 23, 2016
|
|
+ alandekok |
daf05fc
|
arr2036
added a commit
that referenced
this issue
Aug 28, 2016
|
|
+ arr2036 |
cd77189
|
haegar commentedAug 10, 2016
•
edited by arr2036
Issue type
Defect/Feature description
Using two perl {} sections, if the second one contains a config {} section freeradius crashes.
How to reproduce issue
System: Git snapshot from today, including the fix for #1674 Debian Jessie, perl 5.20.2-3+deb8u6
To reproduce the stock configfiles without any change and the following addition are enough:
Create a /etc/freeradius/mods-enabled/zzz-perl-crash:
(No need to use them anywhere to reproduce a crash)
Restart freeradius. (In my case using systemd, with default service file)
Depending on "luck" sometimes results in:
or
or
Output of
[radiusd|freeradius] -Xshowing issue ocurringThis bug does NOT occur if running as "freeradius -X" ! There (with my full config instead of the reduced reproduction settings) it completely works.
Full backtrace from LLDB or GDB