Regarding git bisect. I know the current version is "bad", but I have no idea if any 2.1.8 version is 'Good'. If there a way to use git bisect without identifying 'good'? How can we find the first version? Can we assume it was 'good'? Sorry to be so non knowledgeable about git. -craig ----- Original Message ----- From: "Alexander Clouter" <alex@digriz.org.uk> To: <freeradius-users@lists.freeradius.org> Sent: Friday, November 06, 2009 8:21 AM Subject: Re: Unexpected "Exiting normally" 2.1.8?
Craig Campbell <craig@ccraft.ca> wrote:
[snipped]
I then ran the code from within gdb as Alexander described (within screen - thanks!)
gdb radiusd (gdb) run -f <messages program runs until...> Detaching after fork from child process 14277. Detaching after fork from child process 14334. Detaching after fork from child process 14364. Detaching after fork from child process 14394. Detaching after fork from child process 14424.
Program received signal SIGTERM, Terminated. 0x0000003acf4306a7 in kill () from /lib64/libc.so.6 (gdb) where #0 0x0000003acf4306a7 in kill () from /lib64/libc.so.6 #1 0x0000000000424186 in main (argc=2, argv=0x7fff67ce72d8) at radiusd.c:419 (gdb)
The gdb output is identical for the other radius server.
I'm afraid I haven't helped much. The source I have was acquired Oct 20 15:05 (EST) if that helps in any way. Perhaps I have fewer of the suspected patches in my build than you have in yours? Is there a way we could compare?
Is there any way I can get more information out of these test runs?
Afraid that is all there is to see. If this was a more 'interesting' bug you would get a lot more, but the nature of this particular bug means you do not get much.
Now you have the compiling of FreeRADIUS working and got a successful round of GDB cooking, you need to play with 'git bisect' to pin it down to which patch broke things.
Cheers
-- Alexander Clouter .sigmonster says: You have many friends and very few living enemies.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
__________ Information from ESET Smart Security, version of virus signature database 4578 (20091106) __________
The message was checked by ESET Smart Security.
__________ Information from ESET Smart Security, version of virus signature database 4579 (20091106) __________ The message was checked by ESET Smart Security. http://www.eset.com