From: "Metzger, Markus T via Gdb-patches" <gdb-patches@sourceware.org>
To: Simon Marchi <simon.marchi@polymtl.ca>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH 4/4] testsuite, gdb.btrace: fix 32-bit PIE false positives
Date: Mon, 21 Dec 2020 07:27:08 +0000 [thread overview]
Message-ID: <DM5PR11MB16900275401E31D69A1C533CDEC00@DM5PR11MB1690.namprd11.prod.outlook.com> (raw)
In-Reply-To: <6d4b40f4-31b4-bc99-41a1-36abca520774@polymtl.ca>
Hello Simon,
Thanks for your review.
> > +# We expect a specific function call history. This gets messed up with
> > +# PIE on 32-bit.
> > standard_testfile exception.cc
> > -if [prepare_for_testing "failed to prepare" $testfile $srcfile {c++ debug}] {
> > +if [prepare_for_testing "failed to prepare" $testfile $srcfile \
> > + {additional_flags=-fno-pie ldflags=-no-pie c++ debug}] {
> > return -1
> > }
>
> There's the "nopie" option you can pass to gdb_compile to disable PIE. Although
> from
> what I see, it doesn't add -fno-pie to compilation options, just adds -no-pie to link
> options. I suppose you need both? If so, it could be preferable in the long run to
> teach gdb_compile to pass -fno-pie to the compilation step as well.
Indeed, older GCC require -fno-pie in addition to -no-pie, e.g. GCC 7.5 on Ubuntu 18.04.
I changed the test to use nopie and I'll submit a new patch to add -fno-pie to the
nopie handling of gdb_compile.
Regards,
Markus.
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Gary Kershaw
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next prev parent reply other threads:[~2020-12-21 7:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 15:12 [PATCH] gdb, record: rephrase the 'not recording' error message Markus Metzger via Gdb-patches
2020-12-17 15:12 ` [PATCH 1/4] testsuite, gdb.btrace: make test names unique Markus Metzger via Gdb-patches
2020-12-18 19:34 ` Simon Marchi via Gdb-patches
2020-12-21 7:26 ` Metzger, Markus T via Gdb-patches
2020-12-17 15:12 ` [PATCH 2/4] testsuite, gdb.python: make py-record-*.exp " Markus Metzger via Gdb-patches
2020-12-18 19:35 ` Simon Marchi via Gdb-patches
2020-12-17 15:12 ` [PATCH 3/4] testsuite, gdb.btrace: skip multi-inferior.exp on gdbserver targets Markus Metzger via Gdb-patches
2020-12-18 19:49 ` Simon Marchi via Gdb-patches
2020-12-21 7:27 ` Metzger, Markus T via Gdb-patches
2020-12-21 13:50 ` Simon Marchi via Gdb-patches
2020-12-17 15:12 ` [PATCH 4/4] testsuite, gdb.btrace: fix 32-bit PIE false positives Markus Metzger via Gdb-patches
2020-12-18 20:01 ` Simon Marchi via Gdb-patches
2020-12-21 7:27 ` Metzger, Markus T via Gdb-patches [this message]
2020-12-18 19:18 ` [PATCH] gdb, record: rephrase the 'not recording' error message Simon Marchi via Gdb-patches
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=DM5PR11MB16900275401E31D69A1C533CDEC00@DM5PR11MB1690.namprd11.prod.outlook.com \
--to=gdb-patches@sourceware.org \
--cc=markus.t.metzger@intel.com \
--cc=simon.marchi@polymtl.ca \
/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