Glibc errors causing bzfs to die? I have in recent history had bzfs die with glibc errors. Usually it's right after someone has connected with a string like this:
Player lIFuP2vCdUxSngPQpC98t2VCxuRW10do5sv0dmLuFazU3GDe3MzwVqxW5CN6hoVWFMPM5MbstaLSlU3gRkxSrOdUrsLY1SFqJM52Firux6147gnQfofGPWjcpeRMFMRCZkDyvcvU1kn4pcX6H0fUfS3q3EzeB8RkLiDotM3SliTULiTIfWd4VcxidKJObSP6B4dYP8Z4pEpwr6ZojGRITYLkh8TghyDIRMV8PKHWr0PAvMFOR0ED [2] has joined from 172.216.38.191 at 2006-01-12 03:32:08 with token "5sv0dmLuFazU3GDe3MzwVqxW5CN6hoVWFMPM5MbstaLSlU3gRkxSrOdUrsLY1SFqJM52Firux6147gnQfofGPWjcpeRMFMRCZkDyvcvU1kn4pcX6H0fUfS3q3EzeB8RkLiDotM3SliTULiTIfWd4VcxidKJObSP6B4dYP8Z4pEpwr6ZojGRITYLkh8TghyDIRMV8PKHWr0PAvMFOR0ED"
Player [4] accept() from 69.28.129.166:56153 on 18
Player [4] removed at 2006-01-12 03:32:08: Disconnected
*** glibc detected *** free(): invalid next size (fast): 0x082d07d8 ***
This has happened twice now... any ideas?
A LONG playerid with a LONG token causes bzfs to crash
- badgerking
- Private First Class
- Posts: 98
- Joined: Sat Mar 19, 2005 5:27 pm
- Location: Iowa, USA