public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vincent at bernat dot im" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/26876] gdb error: internal-error: Unknown CFA rule when debugging the linux kernel with qemu
Date: Sat, 28 Aug 2021 20:47:38 +0000	[thread overview]
Message-ID: <bug-26876-4717-fhdNlK5gEs@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26876-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=26876

Vincent Bernat <vincent at bernat dot im> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |vincent at bernat dot im

--- Comment #15 from Vincent Bernat <vincent at bernat dot im> ---
I am running into the same bug with 10.2. I am running gdb from Nix:

```
gdb$  show version
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 "x86_64-unknown-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".
gdb$  show configuration
This GDB was configured as follows:
   configure --host=x86_64-unknown-linux-gnu --target=x86_64-unknown-linux-gnu
             --with-auto-load-dir=$debugdir:$datadir/auto-load
            
--with-auto-load-safe-path=$debugdir:$datadir/auto-load:/nix/store/0kiykyrnrpfhmjwxwx89kxr20hmf5304-gcc-10.3.0-lib
             --with-expat
            
--with-gdb-datadir=/nix/store/wx014fbhv8ssxbn076skz4rwn55qcgpd-gdb-10.2/share/gdb
(relocatable)
            
--with-jit-reader-dir=/nix/store/wx014fbhv8ssxbn076skz4rwn55qcgpd-gdb-10.2/lib/gdb
(relocatable)
             --without-libunwind-ia64
             --without-lzma
             --without-babeltrace
             --with-intel-pt
             --with-mpfr
             --without-xxhash
            
--with-python=/nix/store/nki9ywqzbvz68vr75kn2r7g1q84f5agy-python3-3.9.6
            
--with-python-libdir=/nix/store/nki9ywqzbvz68vr75kn2r7g1q84f5agy-python3-3.9.6/lib
             --without-debuginfod
             --without-guile
             --disable-source-highlight
            
--with-separate-debug-dir=/nix/store/wx014fbhv8ssxbn076skz4rwn55qcgpd-gdb-10.2/lib/debug
(relocatable)

("Relocatable" means the directory can be moved with the GDB installation
tree, and GDB will still find it.)
```

And I am running QEMU 6.1:

```
 22:46 ❱ qemu-system-x86_64 --version
QEMU emulator version 6.1.0 (Debian 1:6.1+dfsg-1)
Copyright (c) 2003-2021 Fabrice Bellard and the QEMU Project developers
```

Also when running `lx-symbols`:

```
gdb$  lx-symbols
loading vmlinux
../../gdb/dwarf2/frame.c:1085: internal-error: Unknown CFA rule.
A problem internal to GDB has been detected,
```

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2021-08-28 20:47 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-13  9:58 [Bug gdb/26876] New: " robert at robertbuhren dot de
2020-11-13 21:35 ` [Bug gdb/26876] " simark at simark dot ca
2020-11-14  2:52 ` simark at simark dot ca
2020-11-14  3:29 ` simark at simark dot ca
2020-11-14  9:06 ` robert at robertbuhren dot de
2020-11-14 17:23 ` simark at simark dot ca
2020-11-14 22:46 ` tromey at sourceware dot org
2020-11-14 23:38 ` simark at simark dot ca
2020-11-15  2:48 ` simark at simark dot ca
2020-11-16 18:21 ` simark at simark dot ca
2020-12-03 19:09 ` simark at simark dot ca
2020-12-03 20:48 ` cvs-commit at gcc dot gnu.org
2020-12-03 20:49 ` simark at simark dot ca
2021-06-27 17:55 ` ahmedsayeed1982 at yahoo dot com
2021-08-19  6:02 ` ucelsanicin at yahoo dot com
2021-08-19 10:31 ` mark at klomp dot org
2021-08-27 18:01 ` ribevi6798 at enamelme dot com
2021-08-28 20:47 ` vincent at bernat dot im [this message]
2021-09-02 10:07 ` josef.grieb at gmail dot com
2021-09-02 11:07 ` donipah907 at mtlcz dot com
2021-09-02 15:23 ` simark at simark dot ca
2021-09-05  7:34 ` kimolsun2020 at yahoo dot com
2021-09-06  9:09 ` focixujo at livinginsurance dot co.uk
2021-09-10 19:39 ` mehmetgelisin at aol dot com
2021-09-26 13:31 ` tes.vik1986 at gmail dot com
2021-10-09  8:47 ` vficaj at ukr dot net
2021-10-09 11:00 ` gulsenenginar at aol dot com
2021-10-18 19:58 ` ahmedsayeed1982 at hotmail 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-11-06 21:12 ` paneki8601 at dukeoo dot com
2021-11-13 19:33 ` tesaso8237 at funboxcn dot com
2021-11-16 19:04 ` xecana8007 at funboxcn dot com
2021-11-16 19:08 ` xecana8007 at funboxcn dot com
2021-11-16 19:12 ` xecana8007 at funboxcn dot com
2021-11-16 19:16 ` xecana8007 at funboxcn dot com
2021-11-16 19:46 ` vincent at bernat dot im
2021-11-22  7:39 ` 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-26876-4717-fhdNlK5gEs@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: 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).