Hello

This week i have discovered where the sys write on closed pipe was  
originating and why. Seems that sometimes, some imap servers, like  
mobileme, respond with an Unknown message codification, and tcs does  
not translate it.

UNKNOWN: charset `UNKNOWN' unknown

The translation is done writting to the stdin of tcs, and it was  
returning that error (writting it to stderr) and closing stdin, so the  
note about writting in closed pipe appeared beause the parent nupas  
was trying to write on the stdin of the forked tcs.

I 'm writting a couple of lines to deal with this. Right now the error  
goes to /dev/null, but i think i would like it to write it to a /sys/ 
log/ file  or something like that.

Also the checkmboxrefs() assert() broke nupas  when two walks are  
issued at the same time, but not allways. There are calls to  
mboxincref there which are not locked (in doclone() and dowalk()). I'm  
doing some tests to clarify this.

While doing theses tests, i've hit a new bug (possibly derivared from  
the tests theirselves):

/proc/44091/text:386 plan 9 executable
/sys/lib/acid/port
/sys/lib/acid/386
acid: stk();
cacheidx(m=0x0,mb=0x0)+0x7 /dist/store/gsoc/src/nupas/fs/cache.c:499
fileinfo(mb=0x0,m=0x0,t=0x0,pp=0xdfffec08)+0x17 /dist/store/gsoc/src/ 
nupas/fs/fs.c:453
mkstat 
(m=0x0,mb=0x0,d=0xdfffec30,t=0x0,hbuf=0x2ba21c,hlen=0x8000)+0xfa /dist/ 
store/gsoc/src/nupas/fs/fs.c:762
rstat(f=0x4adb78,io=0x2b21e0)+0xa6 /dist/store/gsoc/src/nupas/fs/fs.c: 
1455
io(io=0x2b21e0)+0x285 /dist/store/gsoc/src/nupas/fs/fs.c:1557
initio(nprocs=0x5)+0x108 /dist/store/gsoc/src/nupas/fs/fs.c:1613
main(argv=0xdfffefac,argc=0x0)+0x317 /dist/store/gsoc/src/nupas/fs/ 
fs.c:420
_main+0x31 /sys/src/libc/386/main9.s:16
acid: acid:

somehow the mailbox passed to mkstat was nil.

thanks

gabi






--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Plan 
9 Google Summer of Code" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/plan9-gsoc?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to