From: Florian Weimer <fweimer@redhat.com>
To: Abhidnya Joshi <abhidnyachirmule@gmail.com>
Cc: libc-locales@sourceware.org
Subject: Re: Crash in gconv_db.c
Date: Fri, 20 Dec 2019 16:09:00 -0000 [thread overview]
Message-ID: <87r20zf07d.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <CALmqtCXKHrTsAChozkHaDbLohswOpkU9qeTmy=v7nkzKXuR=Kg@mail.gmail.com> (Abhidnya Joshi's message of "Fri, 20 Dec 2019 21:23:23 +0530")
* Abhidnya Joshi:
> The gconv_steps looked like below:
>
> (gdb) p *(&step[1])
> $4 = {__shlib_handle = 0x7f028853b240, __modname = 0x7f028853b270
> "/usr/lib64/gconv/UTF-16.so", __counter = 1, __from_name =
> 0x7f028abca431 "INTERNAL",
> __to_name = 0x7f028853b220 "UTF-16LE//", __fct = 0x59e0be5c0391534f,
> __btowc_fct = 0xa7e5bbe252f1534f, __init_fct = 0x59e0be5c1c91534f,
> __end_fct = 0x59e0be5c03b1534f,
> __min_needed_from = 4, __max_needed_from = 4, __min_needed_to = 2,
> __max_needed_to = 4, __stateful = 0, __data = 0x9bd320}
> (gdb) p *(&step[0])
> $5 = {__shlib_handle = 0x0, __modname = 0x0, __counter = 1,
> __from_name = 0x7f028853b890 "ISO-10646/UTF8/", __to_name =
> 0x7f028abca431 "INTERNAL",
> __fct = 0x7f028aa73ce0 <__gconv_transform_utf8_internal>,
> __btowc_fct = 0x7f028aa714b0 <__gconv_btwoc_ascii>, __init_fct = 0x0,
> __end_fct = 0x0, __min_needed_from = 1,
> __max_needed_from = 6, __min_needed_to = 4, __max_needed_to = 4,
> __stateful = 0, __data = 0x0}
> (gdb)
Since both __counter values are 1, I'm not sure there is a counter
overflow?
What I meant is that it would be nice to have a sequence of glibc API
calls which clearly demonstrate this behavior. I can't reproduce this
with an obvious sequence of iconv calls in a loop.
Thanks,
Florian
next prev parent reply other threads:[~2019-12-20 16:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 16:05 Abhidnya Joshi
2019-11-11 16:19 ` Florian Weimer
2019-11-11 16:47 ` Abhidnya Joshi
[not found] ` <CALmqtCVBCb2vJ+XNb6WZa1csNZaisLmqoG5nTn-QUU0MO=UbPw@mail.gmail.com>
2019-11-14 17:34 ` Florian Weimer
2019-11-19 14:05 ` Abhidnya Joshi
2019-11-28 18:47 ` Abhidnya Joshi
2019-12-12 15:58 ` Florian Weimer
2019-12-20 15:05 ` Abhidnya Joshi
2019-12-20 15:16 ` Florian Weimer
2019-12-20 15:40 ` Abhidnya Joshi
2019-12-20 15:43 ` Florian Weimer
2019-12-20 15:53 ` Abhidnya Joshi
2019-12-20 16:09 ` Florian Weimer [this message]
2019-12-20 16:42 ` Abhidnya Joshi
2019-12-20 16:47 ` Florian Weimer
2019-12-20 17:18 ` Abhidnya Joshi
2019-12-20 18:39 ` Florian Weimer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r20zf07d.fsf@oldenburg2.str.redhat.com \
--to=fweimer@redhat.com \
--cc=abhidnyachirmule@gmail.com \
--cc=libc-locales@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).