public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "jrmuizel at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug tdep/27789] backtraces through unknown functions on m68k are broken Date: Thu, 29 Apr 2021 23:19:50 +0000 [thread overview] Message-ID: <bug-27789-4717-EQjDH5bjwW@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-27789-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=27789 --- Comment #6 from Jeff Muizelaar <jrmuizel at gmail dot com> --- It's possible to just load the attached core file with a gdb that targets m68k-linux (like ubuntu's gdb-multiarch) gdb -c core GNU gdb (GDB) 10.2 Copyright (C) 2021 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "--host=x86_64-pc-linux-gnu --target=m68k-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <https://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word". warning: Can't open file /root/a.out during file-backed mapping note processing warning: Can't open file /usr/lib/m68k-linux-gnu/ld-2.31.so during file-backed mapping note processing warning: Can't open file /usr/lib/m68k-linux-gnu/libc-2.31.so during file-backed mapping note processing [New LWP 395] Core was generated by `./a.out'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x800003be in ?? () (gdb) bt #0 0x800003be in ?? () #1 0xeff50c44 in ?? () #2 0x800003da in ?? () #3 0x00000004 in ?? () #4 0xeff50c50 in ?? () #5 0x800003ec in ?? () #6 0x00000000 in ?? () (gdb) q notice the garbage frames: 1, 3, 4 and 6 Applying the attached patch which does the same thing as 7618e12bcb8f15e83c8c6abc5216f520f09bdbf9 gives: (gdb) bt #0 0x800003be in ?? () #1 0x800003da in ?? () #2 0x800003ec in ?? () #3 0x80000408 in ?? () #4 0xc004a902 in ?? () #5 0x80000346 in ?? () -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-04-29 23:19 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-29 2:19 [Bug tdep/27789] New: " jrmuizel at gmail dot com 2021-04-29 14:11 ` [Bug tdep/27789] " simark at simark dot ca 2021-04-29 17:51 ` jrmuizel at gmail dot com 2021-04-29 17:53 ` jrmuizel at gmail dot com 2021-04-29 18:35 ` simark at simark dot ca 2021-04-29 18:36 ` simark at simark dot ca 2021-04-29 23:19 ` jrmuizel at gmail dot com [this message] 2021-04-29 23:20 ` jrmuizel at gmail dot com 2021-04-30 0:30 ` simark at simark dot ca
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-27789-4717-EQjDH5bjwW@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).