From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20050130 Fedora/1.7.5-3
Description of problem:
When configuring freeradius, an attempt to authenticate against it causes a segfault. An attempt is made to run the program through gdb to get a clue as to the origin of the failure, but the symbols have been stripped and are missing.
A search for a freeradius-debuginfo package comes up empty.
Please publish a debuginfo package so that gdb debugging becomes meaningful.
(The segfault will be posted as a separate bug).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
You can either get the debuginfo package on
Or you can compile for your own. Get the source RPM and make an "rpmbuild --rebuild"
What problems do you have with the authentication?
Please remember that rebuilds and debuginfo packages are not signed and unsupported.
The problem is that I did compile my own package, adding the --enable-developer
within the spec file to get debugging symbols in the hope of getting a
meaningful backtrace, and the server promptly stopped segfaulting and started
There is no documentation anywhere as to where the debuginfo packages are (the
people.redhat.com website is not the first place to look for RPMs). The missing
debuginfo packages mean that I cannot give you feedback about problems with
_redhat_ supported packages - I am now running my own build from SRPM.
The original problem was that when freeradius was set up to use EAP to serve a
wireless access point using WPA via radius via LDAP, the freeradius server would
segfault on the first attempt by a wireless client to connect. I got a
backtrace, but as no symbols were present the backtrace was meaningless.
Assigning to distribution.
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.