Thanks Alan. The backtrace that I sent yesterday comes from a server built with debugging symbols. Here is an extract of our makefile: # to build in developer mode: OPT_ENABLE_DEV = --enable-developer ./configure --prefix=$(FREERADIUS_HOME) \ --with-openssl=no \ --with-talloc-include-dir=$(TALLOC_HOME)/include \ --with-talloc-lib-dir=$(TALLOC_HOME)/lib \ --with-oracle-include-dir=$(ORACLE_HOME)/sdk/include \ --with-oracle-lib-dir=$(ORACLE_HOME) \ --with-libcurl=$(CURL_HOME) \ $(OPT_ENABLE_DEV) Is there something else we should do ? Thanks ! -----Message d'origine----- De : Freeradius-Users [mailto:freeradius-users-bounces+bija.ranjalahy=capgemini.com@lists.freeradius.org] De la part de Alan DeKok Envoyé : mercredi 23 août 2017 00:00 À : FreeRadius users mailing list Objet : Re: Crashes FreeRadius 3.0.11 using rlm_rest/libcurl + rlm_cache_rbtree On Aug 22, 2017, at 9:44 AM, RANJALAHY RASOLOFOMANANA, Bija <bija.ranjalahy@capgemini.com> wrote:
Hi Arran,
1/ For the crash, here is the backtrace :
Re-build the server with debugging symbols. See doc/bugs for details. A stack trace full of opaque hex values and no function names doesn't let us help you. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.