 |
 |
Hi, it looks like the bug is in the command line app. Maybe tomorow I will be able to look into that. Fabrizio Andreas Petzold wrote: > Hi Andy, > > On Wednesday 02 May 2007 21:16:49 Andrew Hanushevsky wrote: >> Hi Andreas, >> >> I assume you are saying the bug is in the client code not the server code, >> yes? > > yes I think so, but I didn't have time to check the code yet. > > Cheers, > > Andreas > >> Andy >> >> ----- Original Message ----- >> From: "Andreas Petzold" <[log in to unmask]> >> To: <[log in to unmask]> >> Sent: Wednesday, May 02, 2007 5:26 AM >> Subject: xrd: buffer overrun when reporting checksum? >> >>> Hi, >>> >>> I've discovered a problem with the xrd interactive xrootd client >>> (20070321-1251). When I request a checksum of a file, the checksum value >>> printed is usually followed by some garbage characters: >>> >>> root://f01-101-118.gridka.de:1094/>getchecksum >>> /prod/subskim/SPskims/SP-Skim-R22V02/000998/200007/49602/S0002/V00/InclPh >>> i.01.root Checksum: crc32 2523947860PE" � >>> >>> I've checked that our checksum script returns a '\n' terminated string as >>> stated in the docs. >>> >>> AFAICT, the perl interface returns the correct checksum value, but I >>> didn't >>> look at the code. >>> >>> Cheers, >>> >>> Andreas > >