[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [bug-gnu-libiconv] RE: [rt.cpan.org #28850] Korean hanging CRITICAL
From: |
Bruno Haible |
Subject: |
Re: [bug-gnu-libiconv] RE: [rt.cpan.org #28850] Korean hanging CRITICAL |
Date: |
Thu, 30 Aug 2007 01:15:29 +0200 |
User-agent: |
KMail/1.5.4 |
> ^CPR_SIGNALLED : Receipt of a traced signal SIGINT: Interrupt (rubout)
>
>
> Program received signal SIGINT, Interrupt.
> 0xfe9f26b0 in unicode_loop_convert () from /usr/local/lib/libiconv.so.2
If you want to prove convincingly that there is a bug in libiconv,
the best way is to look at the arguments being passed to the iconv()
function from libiconv, and write a small C program with the same inputs
and that fails or loops.
Bruno
- [bug-gnu-libiconv] [rt.cpan.org #28850] Korean hanging CRITICAL, Michael Piotrowski via RT, 2007/08/29
- [bug-gnu-libiconv] Re: [rt.cpan.org #28850] Korean hanging CRITICAL, Bruno Haible, 2007/08/29
- [bug-gnu-libiconv] Re: [rt.cpan.org #28850] Korean hanging CRITICAL, address@hidden via RT, 2007/08/29
- [bug-gnu-libiconv] RE: [rt.cpan.org #28850] Korean hanging CRITICAL, Letellier, Aldo, 2007/08/29
- [bug-gnu-libiconv] RE: [rt.cpan.org #28850] Korean hanging CRITICAL, Letellier, Aldo via RT, 2007/08/29
- Re: [bug-gnu-libiconv] RE: [rt.cpan.org #28850] Korean hanging CRITICAL,
Bruno Haible <=
- Re: [bug-gnu-libiconv] RE: [rt.cpan.org #28850] Korean hanging CRITICAL, address@hidden via RT, 2007/08/29
- [bug-gnu-libiconv] [rt.cpan.org #28850] Korean hanging CRITICAL, Michael Piotrowski via RT, 2007/08/30
[bug-gnu-libiconv] RE: [rt.cpan.org #28850] Korean hanging CRITICAL, Letellier, Aldo, 2007/08/29