Commit report for v3.0.x branch
New activity for FreeRADIUS (the high performance and highly configurable RADIUS server) ====== note recent changes Alan T. DeKok@2016-03-15T19:37:35Z Files modified: * doc/ChangeLog Commit diff: https://github.com/FreeRADIUS/freeradius-server/commit/8fc68d868afc22d644e17... ====== Don't call radius_pairmove. It does too much work. Alan T. DeKok@2016-03-15T19:01:04Z Files modified: * src/modules/rlm_sql/rlm_sql.c Commit diff: https://github.com/FreeRADIUS/freeradius-server/commit/8afce710b714ffbed5ce3... ====== note recent changes Alan T. DeKok@2016-03-14T19:20:17Z Files modified: * doc/ChangeLog Commit diff: https://github.com/FreeRADIUS/freeradius-server/commit/5c1b3144ba9a024836b71... ====== -- This commit summary was generated @2016-03-16T00:00:01Z by lgfeed version 0.00 (https://github.com/arr2036/lgfeed).
On 15/03/16 23:00, The git bot wrote:
====== Don't call radius_pairmove. It does too much work.
Alan T. DeKok@2016-03-15T19:01:04Z Files modified: * src/modules/rlm_sql/rlm_sql.c
Commit diff: https://github.com/FreeRADIUS/freeradius-server/commit/8afce710b714ffbed5ce3...
That seems to have fixed my SEGV, many thanks.
On Mar 16, 2016, at 8:48 AM, Phil Mayers <p.mayers@imperial.ac.uk> wrote:
Commit diff: https://github.com/FreeRADIUS/freeradius-server/commit/8afce710b714ffbed5ce3...
That seems to have fixed my SEGV, many thanks.
That doesn't fix the underlying issue, but it does make it much less likely. We'll re-visit it for a later patch. Alan DeKok.
participants (3)
-
Alan DeKok -
announceļ¼ freeradius.org -
Phil Mayers