On Thu, Sep 23, 2010 at 09:37:35AM +0200, Aurelien Jarno wrote: > Stephen Powell a écrit : > > I'm not sure if this bug is in iconv itself or in another package which > > calls iconv, but since I have discovered the problem in at least two > > packages (bash and dash) I will report it against iconv and you may > > reassign it as you see fit. > > > > When looking at the man page for bash or dash, then quitting immediately > > on the first screen by pressing q, I sometimes get the following error > > message: > > > > iconv: conversion stopped due to problem in writing the output > > > > But I can't seem to reproduce the problem consistently. Sometimes I > > get the error, and sometimes I don't. I have yet to come up with a > > scenario that always causes the failure symptoms. > > This message is printed by iconv when data is sent for conversion on > stdin, and stdout is suddenly closed. This is not a problem of iconv, > thus reassigning the bug to man-db.
It's more interesting than that. Normally, iconv should get SIGPIPE when it tries to write to stdout and finds that it's been closed. In normal circumstances that should kill iconv before it prints that message. My leading theory is that Stephen is hitting the format_display_and_save path, which ignores SIGPIPE in the wrong place such that it could be ignored while forking iconv. My secondary theory is that there is something else funny about Stephen's environment such that SIGPIPE is already ignored when starting man. Stephen, can you reproduce this with 'man -d'? If so (or even if not), the output could help me. Also, can you reproduce this under 'strace -f -o man.trace -s 4096'? If so (or even if not), man.trace could help me. Thanks, -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
