public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug backtrace/27017] New: gdb/inline-frame.c:172: internal-error: void inline_frame_this_id
@ 2020-12-04 16:46 dkuhne at hotmail dot de
2020-12-04 16:53 ` [Bug backtrace/27017] " simark at simark dot ca
` (8 more replies)
0 siblings, 9 replies; 10+ messages in thread
From: dkuhne at hotmail dot de @ 2020-12-04 16:46 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=27017
Bug ID: 27017
Summary: gdb/inline-frame.c:172: internal-error: void
inline_frame_this_id
Product: gdb
Version: 10.1
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: backtrace
Assignee: unassigned at sourceware dot org
Reporter: dkuhne at hotmail dot de
Target Milestone: ---
with gdb-multilib 10.1 we still get:
../../gdb/inline-frame.c:172: internal-error: void
inline_frame_this_id(frame_info*, void**, frame_id*): Assertion
`frame_id_p (*this_id)' failed.
A problem internal to GDB has been detected, further debugging may prove
unreliable.
Create a core file of GDB? (y or n)
The core-file we use was generated on AARCH64 Linux-4.9 system, built based on
linaro-6.4-r2017.08 toolchain.
Please let me know any more relevant detail you need.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Bug backtrace/27017] gdb/inline-frame.c:172: internal-error: void inline_frame_this_id
2020-12-04 16:46 [Bug backtrace/27017] New: gdb/inline-frame.c:172: internal-error: void inline_frame_this_id dkuhne at hotmail dot de
@ 2020-12-04 16:53 ` simark at simark dot ca
2020-12-07 7:52 ` dkuhne at hotmail dot de
` (7 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: simark at simark dot ca @ 2020-12-04 16:53 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=27017
Simon Marchi <simark at simark dot ca> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |simark at simark dot ca
--- Comment #1 from Simon Marchi <simark at simark dot ca> ---
Hi Daniel,
A reproducer would be needed to start investigating this. Please provide the
exact source code and commands to use to get to the crash. If you are able to
use tools packaged on common distros, that makes it a bit easier versus a
specific vendor's toolchain.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Bug backtrace/27017] gdb/inline-frame.c:172: internal-error: void inline_frame_this_id
2020-12-04 16:46 [Bug backtrace/27017] New: gdb/inline-frame.c:172: internal-error: void inline_frame_this_id dkuhne at hotmail dot de
2020-12-04 16:53 ` [Bug backtrace/27017] " simark at simark dot ca
@ 2020-12-07 7:52 ` dkuhne at hotmail dot de
2020-12-07 7:54 ` dkuhne at hotmail dot de
` (6 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: dkuhne at hotmail dot de @ 2020-12-07 7:52 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=27017
--- Comment #2 from Daniel Kuhne <dkuhne at hotmail dot de> ---
From:
https://www.cygwin.com/bugzilla/show_bug.cgi?id=25649
it is mentioned:
Reproduction is easy...
"./gdb/gdb gdb/testsuite/outputs/gdb.opt/inline-break/inline-break -ex "b
inline_func1" -ex "run"
and:
This may be a gcc bug for aarch64-linux.
Patch sent.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Bug backtrace/27017] gdb/inline-frame.c:172: internal-error: void inline_frame_this_id
2020-12-04 16:46 [Bug backtrace/27017] New: gdb/inline-frame.c:172: internal-error: void inline_frame_this_id dkuhne at hotmail dot de
2020-12-04 16:53 ` [Bug backtrace/27017] " simark at simark dot ca
2020-12-07 7:52 ` dkuhne at hotmail dot de
@ 2020-12-07 7:54 ` dkuhne at hotmail dot de
2020-12-07 9:17 ` dkuhne at hotmail dot de
` (5 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: dkuhne at hotmail dot de @ 2020-12-07 7:54 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=27017
--- Comment #3 from Daniel Kuhne <dkuhne at hotmail dot de> ---
(In reply to Simon Marchi from comment #1)
> Hi Daniel,
>
> A reproducer would be needed to start investigating this. Please provide
> the exact source code and commands to use to get to the crash. If you are
> able to use tools packaged on common distros, that makes it a bit easier
> versus a specific vendor's toolchain.
We can't share the corefile and the application. We need to find small demo to
reproduce. But please see my other comment about
https://www.cygwin.com/bugzilla/show_bug.cgi?id=25649
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Bug backtrace/27017] gdb/inline-frame.c:172: internal-error: void inline_frame_this_id
2020-12-04 16:46 [Bug backtrace/27017] New: gdb/inline-frame.c:172: internal-error: void inline_frame_this_id dkuhne at hotmail dot de
` (2 preceding siblings ...)
2020-12-07 7:54 ` dkuhne at hotmail dot de
@ 2020-12-07 9:17 ` dkuhne at hotmail dot de
2020-12-07 9:23 ` dkuhne at hotmail dot de
` (4 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: dkuhne at hotmail dot de @ 2020-12-07 9:17 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=27017
--- Comment #4 from Daniel Kuhne <dkuhne at hotmail dot de> ---
Program terminated with signal SIGABRT, Aborted.
#0 0x0000007f9dd13e9c in ?? ()
[Current thread is 1 (LWP 959)]
(gdb) bt
#0 0x0000007f9dd13e9c in ?? ()
#1 0x0000000000004000 in ?? ()
frame#1 is very strange here?!
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Bug backtrace/27017] gdb/inline-frame.c:172: internal-error: void inline_frame_this_id
2020-12-04 16:46 [Bug backtrace/27017] New: gdb/inline-frame.c:172: internal-error: void inline_frame_this_id dkuhne at hotmail dot de
` (3 preceding siblings ...)
2020-12-07 9:17 ` dkuhne at hotmail dot de
@ 2020-12-07 9:23 ` dkuhne at hotmail dot de
2020-12-07 9:34 ` dkuhne at hotmail dot de
` (3 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: dkuhne at hotmail dot de @ 2020-12-07 9:23 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=27017
--- Comment #5 from Daniel Kuhne <dkuhne at hotmail dot de> ---
(In reply to Daniel Kuhne from comment #4)
> Program terminated with signal SIGABRT, Aborted.
> #0 0x0000007f9dd13e9c in ?? ()
> [Current thread is 1 (LWP 959)]
> (gdb) bt
> #0 0x0000007f9dd13e9c in ?? ()
> #1 0x0000000000004000 in ?? ()
>
> frame#1 is very strange here?!
this is w/ aarch64-linux-gnu-gdb 10.1-2 from archlinux,
with the one which comes with linaro-6.4 I get:
#0 0x0000007f9dd13e9c in ?? ()
[Current thread is 1 (LWP 959)]
(gdb) bt
#0 0x0000007f9dd13e9c in ?? ()
#1 0x0000007f9dd13e28 in ?? ()
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Bug backtrace/27017] gdb/inline-frame.c:172: internal-error: void inline_frame_this_id
2020-12-04 16:46 [Bug backtrace/27017] New: gdb/inline-frame.c:172: internal-error: void inline_frame_this_id dkuhne at hotmail dot de
` (4 preceding siblings ...)
2020-12-07 9:23 ` dkuhne at hotmail dot de
@ 2020-12-07 9:34 ` dkuhne at hotmail dot de
2020-12-07 11:43 ` dkuhne at hotmail dot de
` (2 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: dkuhne at hotmail dot de @ 2020-12-07 9:34 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=27017
--- Comment #6 from Daniel Kuhne <dkuhne at hotmail dot de> ---
(In reply to Daniel Kuhne from comment #5)
> (In reply to Daniel Kuhne from comment #4)
> > Program terminated with signal SIGABRT, Aborted.
> > #0 0x0000007f9dd13e9c in ?? ()
> > [Current thread is 1 (LWP 959)]
> > (gdb) bt
> > #0 0x0000007f9dd13e9c in ?? ()
> > #1 0x0000000000004000 in ?? ()
> >
> > frame#1 is very strange here?!
>
> this is w/ aarch64-linux-gnu-gdb 10.1-2 from archlinux,
> with the one which comes with linaro-6.4 I get:
>
> #0 0x0000007f9dd13e9c in ?? ()
> [Current thread is 1 (LWP 959)]
> (gdb) bt
> #0 0x0000007f9dd13e9c in ?? ()
> #1 0x0000007f9dd13e28 in ?? ()
Program terminated with signal SIGABRT, Aborted.
#0 0x0000007f9dd13e9c in ?? ()
[Current thread is 1 (LWP 959)]
(gdb) add-symbol-file libc-2.24.so 0x7f9dce3000+0x1ed00
add symbol table from file "libc-2.24.so" at
.text_addr = 0x7f9dd01d00
(y or n) y
Reading symbols from libc-2.24.so...done.
(gdb) bt
#0 __GI_raise (sig=6) at
/usr/src/debug/glibc/2.24-r0/git/sysdeps/unix/sysv/linux/raise.c:58
#1 0x0000007f9dd13e28 in __libc_signal_block_app (set=0x55b899c390) at
/usr/src/debug/glibc/2.24-r0/git/sysdeps/unix/sysv/linux/nptl-signals.h:67
#2 __GI_raise (
../../gdb-7.11.1/gdb/inline-frame.c:167: internal-error: inline_frame_this_id:
Assertion `frame_id_p (*this_id)' failed.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Bug backtrace/27017] gdb/inline-frame.c:172: internal-error: void inline_frame_this_id
2020-12-04 16:46 [Bug backtrace/27017] New: gdb/inline-frame.c:172: internal-error: void inline_frame_this_id dkuhne at hotmail dot de
` (5 preceding siblings ...)
2020-12-07 9:34 ` dkuhne at hotmail dot de
@ 2020-12-07 11:43 ` dkuhne at hotmail dot de
2020-12-07 12:43 ` luis.machado at linaro dot org
2020-12-08 18:28 ` simark at simark dot ca
8 siblings, 0 replies; 10+ messages in thread
From: dkuhne at hotmail dot de @ 2020-12-07 11:43 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=27017
--- Comment #7 from Daniel Kuhne <dkuhne at hotmail dot de> ---
turns out it is related to loading the debug version of libc-2.24.so
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Bug backtrace/27017] gdb/inline-frame.c:172: internal-error: void inline_frame_this_id
2020-12-04 16:46 [Bug backtrace/27017] New: gdb/inline-frame.c:172: internal-error: void inline_frame_this_id dkuhne at hotmail dot de
` (6 preceding siblings ...)
2020-12-07 11:43 ` dkuhne at hotmail dot de
@ 2020-12-07 12:43 ` luis.machado at linaro dot org
2020-12-08 18:28 ` simark at simark dot ca
8 siblings, 0 replies; 10+ messages in thread
From: luis.machado at linaro dot org @ 2020-12-07 12:43 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=27017
Luis Machado <luis.machado at linaro dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |luis.machado at linaro dot org
--- Comment #8 from Luis Machado <luis.machado at linaro dot org> ---
I gave this a try and couldn't reproduce the failures for
gdb.opt/inline-break.exp.
What exactly is gdb-multilib 10.1? What is it targetting?
A build for aarch64-linux didn't show the problem, like I said.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Bug backtrace/27017] gdb/inline-frame.c:172: internal-error: void inline_frame_this_id
2020-12-04 16:46 [Bug backtrace/27017] New: gdb/inline-frame.c:172: internal-error: void inline_frame_this_id dkuhne at hotmail dot de
` (7 preceding siblings ...)
2020-12-07 12:43 ` luis.machado at linaro dot org
@ 2020-12-08 18:28 ` simark at simark dot ca
8 siblings, 0 replies; 10+ messages in thread
From: simark at simark dot ca @ 2020-12-08 18:28 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=27017
--- Comment #9 from Simon Marchi <simark at simark dot ca> ---
Since the failure happens in raise, can you reproduce the bug if you make a
dummy application that calls abort()? If so, you could probably share that +
your libc.so file, and we will probably be able to reproduce it.
Also, make sure you test with GDB master, in case the bug has been fixed
recently.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2020-12-08 18:28 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-12-04 16:46 [Bug backtrace/27017] New: gdb/inline-frame.c:172: internal-error: void inline_frame_this_id dkuhne at hotmail dot de
2020-12-04 16:53 ` [Bug backtrace/27017] " simark at simark dot ca
2020-12-07 7:52 ` dkuhne at hotmail dot de
2020-12-07 7:54 ` dkuhne at hotmail dot de
2020-12-07 9:17 ` dkuhne at hotmail dot de
2020-12-07 9:23 ` dkuhne at hotmail dot de
2020-12-07 9:34 ` dkuhne at hotmail dot de
2020-12-07 11:43 ` dkuhne at hotmail dot de
2020-12-07 12:43 ` luis.machado at linaro dot org
2020-12-08 18:28 ` simark at simark dot ca
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).