From: Abhidnya Joshi <abhidnyachirmule@gmail.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: libc-locales@sourceware.org
Subject: Re: Crash in gconv_db.c
Date: Mon, 11 Nov 2019 16:47:00 -0000 [thread overview]
Message-ID: <CALmqtCWfnPZ=B2=_VM=uqAgMWqh3FbGjxXLcbg466Tgct+dUVw@mail.gmail.com> (raw)
In-Reply-To: <87bltiv10t.fsf@oldenburg2.str.redhat.com>
This is not reproducible. Its happening in customer environment. I
tried sample iconv program just to understand the flow. But when I
execute this, it takes little different path.
I am afraid I do not understand iconv details much. What else I can do
to detect corruption?
Thanks
Abhidnya
On Mon, Nov 11, 2019 at 9:49 PM Florian Weimer <fweimer@redhat.com> wrote:
>
> * Abhidnya Joshi:
>
> > The questions here are:
> > 1. why step[0] has counter 1? this means it was 0, got incremented via
> > increment_counter and hence getting inside
> >
> > DL_CALL_FCT (init_fct, (step));
> >
> > 2. When step gets initialized, counter is never 0. Under which
> > condition this can become 0?
> > 3. Please let me know what to debug more to understand this.
>
> First, we should rule out that this isn't the result of unrelated heap
> corruption. Do you have reproducer? Can you run under valgrind or
> built with Address Sanitizer?
>
> Thanks,
> Florian
>
next prev parent reply other threads:[~2019-11-11 16:47 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 [this message]
[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
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='CALmqtCWfnPZ=B2=_VM=uqAgMWqh3FbGjxXLcbg466Tgct+dUVw@mail.gmail.com' \
--to=abhidnyachirmule@gmail.com \
--cc=fweimer@redhat.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).