public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "robert at robertbuhren dot de" <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, 14 Nov 2020 09:06:42 +0000	[thread overview]
Message-ID: <bug-26876-4717-rhSDMkn9T9@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26876-4717@http.sourceware.org/bugzilla/>

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

--- Comment #4 from robert at robertbuhren dot de ---
Hi, 
thanks for looking into this. I forgot to include my qemu setup, sorry for
that. There is no need to use any kind of guest OS to trigger the bug:

qemu-system-x86_64 -enable-kvm -m 4096 -smp 1 -kernel
linux/arch/x86/boot/bzImage -append "console=ttyS0 nokaslr" -S -s -nographic
-monitor tcp::4444,server,nowait -serial stdio

I let the kernel boot (it will panic because there is no /init to execute) and
then simply stop it via "CTRL-C": 

GNU gdb (GDB) 10.1
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/g>
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-pc-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) file vmlinux
Reading symbols from vmlinux...
(gdb) tar rem :1234
Remote debugging using :1234
0x000000000000fff0 in exception_stacks ()
(gdb) c
Continuing.
^C
Program received signal SIGINT, Interrupt.
0xffffffff814222e0 in rdtsc_ordered ()
    at ./arch/x86/include/asm/msr.h:234
234             asm volatile(ALTERNATIVE_2("rdtsc",
(gdb) lx-symbols 
loading vmlinux
../../gdb/dwarf2/frame.c:1085: internal-error: Unknown CFA rule.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) y
This is a bug, please report it.  For instructions, see:
<https://www.gnu.org/software/gdb/bugs/>.

../../gdb/dwarf2/frame.c:1085: internal-error: Unknown CFA rule.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) y
fish: “gdb” terminated by signal SIGABRT (Abort)

Regards,
Robert

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

  parent reply	other threads:[~2020-11-14  9:06 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 [this message]
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
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-rhSDMkn9T9@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).