On Mon, Jun 9, 2014 at 9:43 PM, Arran Cudbard-Bell <a.cudbardb@freeradius.org> wrote:
On 9 Jun 2014, at 15:09, Enrique Sainz Baixauli <enriquesainz.beca@intef.educacion.es> wrote:
Then it goes on to another module and prints those messages again. So I wonder why this fails (or doesn't get to end) in my system but runs peacefully in yours :S
IIRC your last issue was incorrect server time, causing the build system to behave erratic (due to files with timestamp in the future). Have you fixed that?
Thanks guys, I totally forgot about the time issue... there were no warnings about that though (but they were there last time I tried, right?), but now it's already CCing everything into place :)
So I built it, installed the packages I needed and got a new segfault... now it happens on request (6) instead of (5), but I'm not sure if that's relevant. Anyway, this is the debug output:
./configure --enable-developer
It's hitting a bunch of soft asserts in the freeradius library which would launch the debugger if --enable-developer were set.
If we can get the backtrace from one of those we might have a better idea about what's going on.
Would it make sense to enable the flag on all bundled package recipes? IIRC 2.x debian/rules has it (official debian/ubuntu package has it as well), but 3.0.x doesn't. Haven't checked others though. -- Fajar