From: Simon Marchi <simark@simark.ca>
To: mlimber <mlimber@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] [PR 25678] gdb crashes with "internal-error: sect_index_text not initialized" when .text
Date: Thu, 14 May 2020 15:28:07 -0400 [thread overview]
Message-ID: <59eeb6ee-1ab2-e5aa-000a-2fb6d522b8d0@simark.ca> (raw)
In-Reply-To: <CAAogRRoTkUQdRiMu9jx9LZinSaQAX1nvWF51wYhidzzi39vs+Q@mail.gmail.com>
On 2020-05-14 3:12 p.m., mlimber via Gdb-patches wrote:
> Unfortunately, the simpler repro cases I have tried don't trigger the
> failure, e.g.,
>
> // main.c
> extern int g_global_var;
> int main()
> {
> return g_global_var;
> }
>
> // libglobal.c
> extern int g_global_var;
> int g_global_var = 42;
>
> I build it like:
>
> gcc -shared -nostdlib -fPIC -o libglobal.so libglobal.c
> gcc -o main main.c -lglobal -L. -Wl,--rpath,\$ORIGIN
>
> Running it in GDB works fine. Seems like something more is required.
>
> Even following the repro steps listed in the first comment or linking
> against libicudata.so in a simple program like above work fine for me.
>
> My more complicated, real-world use case does consistently repro the bug
> before the patch but does not after.
>
> More digging required. Suggestions welcome!
>
> M
If you can make a reproducer that uses Qt, that's a good start. Then we can
track down what's special about this use case, and try to make a reproducer
that doesn't use it.
But for the record, I was able to reproduce the crash using the instructions
in the bug. Keith (comment 3) did too.
Simon
next prev parent reply other threads:[~2020-05-14 19:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 17:22 mlimber
2020-05-14 17:32 ` Simon Marchi
2020-05-14 17:48 ` mlimber
2020-05-14 17:57 ` Simon Marchi
2020-05-14 19:12 ` mlimber
2020-05-14 19:28 ` Simon Marchi [this message]
2020-05-15 18:33 ` mlimber
2020-05-16 20:39 ` mlimber
2020-05-16 21:05 ` Simon Marchi
2020-05-17 3:31 ` Simon Marchi
2020-05-17 7:01 ` Andreas Schwab
2020-05-17 14:01 ` Simon Marchi
2020-05-17 14:08 ` Simon Marchi
2020-05-18 18:01 ` Simon Marchi
2020-05-18 21:11 ` mlimber
2020-05-18 21:44 ` Simon Marchi
2020-05-19 14:36 ` mlimber
2020-05-19 14:44 ` Simon Marchi
2020-05-20 13:24 ` mlimber
2020-05-20 14:12 ` Simon Marchi
2020-05-20 15:04 ` mlimber
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=59eeb6ee-1ab2-e5aa-000a-2fb6d522b8d0@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=mlimber@gmail.com \
/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).