Bug#234691: Processed: Re: Bug#234691: mkisofs: SIGBUS on sparc32
At Mon, 15 Mar 2004 18:03:44 -0800,
Joshua Kwan wrote:
> On Fri, Mar 12, 2004 at 04:34:28PM +0900, GOTO Masanori wrote:
> > auric? It's woody machine. There's no dchroot. Please test this bug
> > on the latest sid machine.
>
> I'm providing a gdb backtrace below on the same sparc32 box.
Is this gdb result on auric? You wrote your backtrace was executed on
"auric.debian.org" in the previous mail. But look at
http://db.debian.org/machines.cgi. "auric.debian.org" is woody.
> Program received signal SIGBUS, Bus error.
> 0x5004dd68 in __gconv_get_alias_db () from /lib/libc.so.6
> (gdb) bt
> #0 0x5004dd68 in __gconv_get_alias_db () from /lib/libc.so.6
> #1 0x501bdca8 in gconv () from /usr/lib/gconv/ISO8859-1.so
> #2 0x5004729c in iconv_close () from /lib/libc.so.6
Is this gdb result on woody machine, not sid?
> > Which locales did you use? Which strings did you test? We can easily
> > re-inspect whether this bug is sid iconv(3) issue or not. Did you
> > test it?
>
> $ echo $LANG
> en_US.ISO-8859-1
> $ echo $LC_ALL
> en_US.ISO-8859-1
>
> I'm not sure what you mean by "which strings did you test".
What strings did you give to iconv(3)? What procedures do we
reproduce this bug?
> This is latest and greatest sid here. Also this differs from original
> bug report in that I am now using kernel 2.6.4 on the machine.
I would like to know how to reproduce this bug. Please provide us the
sample program if you can. If ISO-8859-1 gconv has bug, then I guess
many users also get the problem.
Regards,
-- gotom
Reply to: