Just to follow up, this was fixed with v1.9 of src/lib/libc/stdio/findfp.c
Thanks Maxim !
I've cc'd -current as I think something more sinister is going on.
To recap, I'm having trouble running xsane on -current from about two
days ago. fopen() is failing...
The attached patch
In message [EMAIL PROTECTED] Farid Hajji writes:
: dev.lan.Awfulhak.org kernel log messages:
: microuptime() went backwards (18415.166882 - 18415.158249)
: microuptime() went backwards (18490.192910 - 18490.187579)
: microuptime() went backwards (19572.644000 - 19572.638237)
:
dev.lan.Awfulhak.org kernel log messages:
microuptime() went backwards (18415.166882 - 18415.158249)
microuptime() went backwards (18490.192910 - 18490.187579)
microuptime() went backwards (19572.644000 - 19572.638237)
microuptime() went backwards (19878.637972 - 19878.637330)
On Wed, Feb 07, 2001 at 12:34:18AM +0100, Farid Hajji wrote:
I'm also seing this as of CURRENT-2001-01-27 and later:
pcm1: hwptr went backwards 36 - 0
pcm1: hwptr went backwards 40 - 16
pcm1: hwptr went backwards 2084 - 2048
pcm1: hwptr went backwards 2092 - 2064
These have existed
Hi,
Would you mind if I commit the attached patch for the xsane port ?
It makes sense - rather than dropping a core when fopen() fails (and
fclose() is called with a NULL arg). It happens when your home
directory isn't writable :-/
I've cc'd -current as I think something more
I've cc'd -current as I think something more sinister is going on.
To recap, I'm having trouble running xsane on -current from about two
days ago. fopen() is failing...
The attached patch exposes more about what's wrong. Interestingly
enough, the file it's trying to create is in /tmp
lstat("/tmp//preview-level-0-15-b924dc",0xbfbfe894) ERR#2 'No such file or directory'
^^
surely this is not nice!! My guess is that the double slash is confusing
everything...
Anyway, I'm more interested in below:
@@ -2830,9 +2831,17 @@
if (preview_make_image_path(p,
