On Fri, 2003-08-29 at 10:03, Philip Blundell wrote: > On Fri, 2003-08-29 at 08:54, Thomas Morin wrote: > > I can't reproduce the segfault if I upgrade to console-tools 1:0.2.3dbs-41, > > but I guess this was quite expected since this bug seems to hit binaries > > compiled with older glibc, non ? > > Kind of. The particular fseek() bug that broke win4lin and so on was > indeed specific to binaries compiled with older versions of glibc. > However, even console-tools 1:0.2.3-23.3 was not compiled with an old > enough version to run into that problem, and I am able to reproduce the > segfault even if I recompile 1:0.2.3-23.3 from source and link it with > the very latest libc. > > So, it looks to me like this is a bona fide bug in the older > console-tools, not a problem with glibc. My guess is that it is calling > fclose() twice on the same file descriptor, or something like that. > As the console-tools maintainer, maybe I can shed some light. The older console-tools did indeed have a bug, revealed by the glibc 2.3.2 upload: it did double fclose() a fd. Under older glibc's, this was a null op; now it segfaults.
Sorry about not joining earlier; I've moved house and lose 'net connectivity. Regards, Alastair > p. -- Alastair McKinstry <[EMAIL PROTECTED]> GPG Key fingerprint = 9E64 E714 8E08 81F9 F3DC 1020 FA8E 3790 9051 38F4 He that would make his own liberty secure must guard even his enemy from oppression; for if he violates this duty he establishes a precedent that will reach to himself. - --Thomas Paine -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
