public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tes.vik1986 at gmail dot com" <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: Sun, 26 Sep 2021 13:31:30 +0000 [thread overview]
Message-ID: <bug-26876-4717-V2pQ8tbKDx@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26876-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26876
Kylan <tes.vik1986 at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tes.vik1986 at gmail dot com
--- Comment #22 from Kylan <tes.vik1986 at gmail dot com> ---
amd64-linux-siginfo.c: Adjust include order to avoid gnulib error
On Fedora rawhide, after updating to glibc-2.33, I'm seeing the
following build failure: https://komiya-dental.com/crypto/new-coins/
CXX nat/amd64-linux-siginfo.o
http://www-look-4.com/property/houses-in-france/
In file included from /usr/include/bits/sigstksz.h:24,
from /usr/include/signal.h:315,
http://www.iu-bloomington.com/property/properties-in-turkey/
from ../gnulib/import/signal.h:52,
from
/ironwood1/sourceware-git/rawhide-gnulib/bld/../../worktree-gnulib/gdbserver/../gdb/nat/amd64-linux-siginfo.c:20:
https://www.webb-dev.co.uk/services/vaccine-services/
../gnulib/import/unistd.h:663:3: error: #error "Please include config.h
first." https://waytowhatsnext.com/shopping/xbox-release-date/
663 | #error "Please include config.h first."
| ^~~~~ http://www.acpirateradio.co.uk/technology/global-warming/
glibc-2.33 has changed signal.h to now include <bits/sigstksz.h> which,
http://www.logoarts.co.uk/travel/actions-camera/
in turn, includes <unistd.h>. For a gdb build, this causes the gnulib
http://www.slipstone.co.uk/category/technology/
version of unistd.h to be pulled in first. The build failure shown
http://embermanchester.uk/computers/video-conversation/
above happens because gnulib's config.h has not been included before
the include of <signal.h>. http://connstr.net/health/usb-chargers/
The fix is simple - we just rearrange the order of the header file
http://joerg.li/services/kia-rio-price/
includes to make sure that gdbsupport/commondefs.h is included before
attempting to include signal.h. Note that gdbsupport/commondefs.h
http://www.jopspeech.com/technology/thunderbolt-4/
includes <gnulib/config.h>.
Build and regression tested on Fedora 33. On Fedora rawhide, GDB
http://www.wearelondonmade.com/technology/van-technology/
builds again. amd64-linux-siginfo.c: Adjust include order to avoid gnulib
error
http://www.compilatori.com/technology/download-videos/
On Fedora rawhide, after updating to glibc-2.33, I'm seeing the
following build failure:
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-09-26 13:31 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
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 [this message]
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-V2pQ8tbKDx@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).