I was able to get some bisect runs (I think). However, I am encountering a different error in these. If radiusd is run in multithreaded mode, it hangs shortly after beginning. This particular error has already been fixed (later). Do you know if the Signal/Exit error depends upon multi threading? i.e will it happen if run with the -s option? I'm trying to determine a strategy to find close in on the error we are interested in. Thanks, -craig ----- Original Message ----- From: "Craig Campbell" <craig@ccraft.ca> To: "FreeRadius users mailing list" <freeradius-users@lists.freeradius.org> Sent: Friday, November 06, 2009 11:43 AM Subject: Re: Unexpected "Exiting normally" 2.1.8?
I'm afraid I did something incorrect.
I ended up with,
gcc -o .libs/radmin .libs/radmin.o /usr/lib/libreadline.so /usr/lib/libtermcap.so .libs/util.o .libs/log.o .libs/conffile.o /home/craig/src/freeradius/freeradius-server/src/lib/.libs/libfreeradius-radius.so -lnsl -lresolv -lpthread -lreadline -ltermcap -Wl,--rpath -Wl,/usr/local/lib /usr/lib/libreadline.so: could not read symbols: File in wrong format collect2: ld returned 1 exit status
Which I suspect is result of my git bisect attempts....
$git bisect start $git bisect bad $git bisect good 9261f3e0026323b2c397af13d02fbc5780908143
$git bisect loggit bisect start # bad: [1489f5ffa5835e001499ee4f7a5f50a0da375613] Conf for debugging git bisect bad 1489f5ffa5835e001499ee4f7a5f50a0da375613 # good: [9261f3e0026323b2c397af13d02fbc5780908143] Ensure that there is a cleanup event for proxied packets git bisect good 9261f3e0026323b2c397af13d02fbc5780908143 # good: [9261f3e0026323b2c397af13d02fbc5780908143] Ensure that there is a cleanup event for proxied packets git bisect good 9261f3e0026323b2c397af13d02fbc5780908143
$git bisect next $CFLAGS='-O0 -g' ./configure $make clean $make ..... gcc -o .libs/radmin .libs/radmin.o /usr/lib/libreadline.so /usr/lib/libtermcap.so .libs/util.o .libs/log.o .libs/conffile.o /home/craig/src/freeradius/freeradius-server/src/lib/.libs/libfreeradius-radius.so -lnsl -lresolv -lpthread -lreadline -ltermcap -Wl,--rpath -Wl,/usr/local/lib /usr/lib/libreadline.so: could not read symbols: File in wrong format collect2: ld returned 1 exit status
----- Original Message ----- From: "Alexander Clouter" <alex@digriz.org.uk> To: <freeradius-users@lists.freeradius.org> Sent: Friday, November 06, 2009 10:15 AM Subject: Re: Unexpected "Exiting normally" 2.1.8?
Craig Campbell <craig@ccraft.ca> wrote:
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.
Please read my original email listing all the git cherry picks that I used.
Cheers
-- Alexander Clouter .sigmonster says: Logic is a pretty flower that smells bad.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
__________ Information from ESET Smart Security, version of virus signature database 4579 (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.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
__________ Information from ESET Smart Security, version of virus signature database 4579 (20091106) __________
The message was checked by ESET Smart Security.
__________ Information from ESET Smart Security, version of virus signature database 4580 (20091106) __________ The message was checked by ESET Smart Security. http://www.eset.com