public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug backtrace/27147] [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors) Date: Mon, 04 Jan 2021 18:58:28 +0000 [thread overview] Message-ID: <bug-27147-4717-PW6WNw5gkS@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-27147-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=27147 Simon Marchi <simark at simark dot ca> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2021-01-04 Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Target Milestone|--- |10.2 --- Comment #3 from Simon Marchi <simark at simark dot ca> --- Ok, I was able to reproduce this on gcc102, on the gcc compile farm. It bisected to 5b6d1e4fa4fc ("Multi-target support"). At 5b6d1e4fa4fc: $ ./binutils-gdb/gdb/gdb --data-directory binutils-gdb/gdb/data-directory -batch a.out -ex "b puts" -ex "r" -ex "bt" Breakpoint 1 at 0x1021a0 Breakpoint 1, 0xffff80010019c63c in puts () from /lib/sparc64-linux-gnu/libc.so.6 #0 0xffff80010019c63c in puts () from /lib/sparc64-linux-gnu/libc.so.6 #1 0x000007feffdee2d9 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) At 5b6d1e4fa4fc^: ./binutils-gdb/gdb/gdb --data-directory binutils-gdb/gdb/data-directory -batch a.out -ex "b puts" -ex "r" -ex "bt" Breakpoint 1 at 0x1021a0 Breakpoint 1, 0xffff80010019c63c in puts () from /lib/sparc64-linux-gnu/libc.so.6 #0 0xffff80010019c63c in puts () from /lib/sparc64-linux-gnu/libc.so.6 #1 0x00000100000007f8 in hello () at test.c:4 #2 0x0000010000000810 in main () at test.c:8 Since this is a 9 -> 10 regression, I'll mark it with the 10.2 milestone. I don't plan to look more into it at the moment. Note: I tried to generate a core file, to be able to analyze further on my local machine, but I wasn't able to load it. GDB doesn't find the registers in the core file: warning: Couldn't find general-purpose registers in core file. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-01-04 18:58 UTC|newest] Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-04 12:57 [Bug backtrace/27147] New: " koachan+sourceware at protonmail dot com 2021-01-04 15:58 ` [Bug backtrace/27147] " simark at simark dot ca 2021-01-04 16:26 ` simark at simark dot ca 2021-01-04 18:58 ` simark at simark dot ca [this message] 2021-01-04 23:41 ` koachan+sourceware at protonmail dot com 2021-01-04 23:42 ` koachan+sourceware at protonmail dot com 2021-02-18 17:35 ` simark at simark dot ca 2021-02-23 17:48 ` andrew.burgess at embecosm dot com 2021-02-23 18:23 ` andrew.burgess at embecosm dot com 2021-02-23 18:32 ` simark at simark dot ca 2021-02-23 18:33 ` simark at simark dot ca 2021-02-24 9:50 ` andrew.burgess at embecosm dot com 2021-02-24 21:34 ` simark at simark dot ca 2021-02-24 23:39 ` simark at simark dot ca 2021-03-04 0:49 ` simark at simark dot ca 2021-03-04 12:27 ` koachan+sourceware at protonmail dot com 2021-03-04 16:07 ` cvs-commit at gcc dot gnu.org 2021-03-04 17:08 ` cvs-commit at gcc dot gnu.org 2021-03-04 17:09 ` simark at simark dot ca 2021-03-04 17:09 ` simark at simark dot ca 2021-06-27 17:46 ` ahmedsayeed1982 at yahoo dot com 2021-08-10 11:45 ` ucelsanicin at yahoo dot com 2021-08-27 17:52 ` ribevi6798 at enamelme dot com 2021-08-28 18:31 ` buranlevent at yahoo dot com 2021-09-06 9:10 ` focixujo at livinginsurance dot co.uk 2021-09-10 19:40 ` mehmetgelisin at aol dot com 2021-09-14 17:29 ` johnb6174 at gmail dot com 2021-09-14 18:48 ` mark at klomp dot org 2021-09-26 13:31 ` tes.vik1986 at gmail dot com 2021-10-09 11:00 ` gulsenenginar at aol dot com 2021-10-10 16:10 ` oficaj3 at gmail dot com 2021-10-19 7:14 ` progonsaytu at gmail dot com 2021-10-23 13:46 ` fiteva5725 at bomoads dot com 2021-10-24 10:02 ` glassmtech at ukr dot net 2021-10-29 10:57 ` kimolsun2020 at outlook dot com 2021-10-29 12:07 ` huracantili20 at gmail dot com 2021-11-02 15:21 ` gepaw63633 at dukeoo dot com 2021-11-06 21:12 ` paneki8601 at dukeoo dot com 2021-11-16 19:05 ` xecana8007 at funboxcn dot com 2021-11-16 19:08 ` xecana8007 at funboxcn dot com 2021-11-22 7:37 ` gexed96894 at keagenan dot com
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=bug-27147-4717-PW6WNw5gkS@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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: linkBe 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).