From: Kevin Buettner <kevinb@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org, simark@simark.ca
Subject: Re: The 'cold' function attribute and GDB
Date: Thu, 02 May 2019 15:59:00 -0000 [thread overview]
Message-ID: <20190502085919.63b2d520@f29-4.lan> (raw)
In-Reply-To: <83lfzoq3ly.fsf@gnu.org>
On Thu, 02 May 2019 18:26:49 +0300
Eli Zaretskii <eliz@gnu.org> wrote:
> > Date: Thu, 2 May 2019 00:26:44 -0700
> > From: Kevin Buettner <kevinb@redhat.com>
> > Cc: gdb-patches@sourceware.org, Simon Marchi <simark@simark.ca>
> >
> > https://www.sourceware.org/ml/gdb-patches/2018-08/msg00541.html
> >
> > It's possible that more needs to be done with display of addresses.
> > I'll need to look at it more closely to know for sure. It would help
> > me if there were a relatively small test case to look at. (It would
> > help even more if it could be reproduced on a GNU/Linux system.)
>
> I tried to write a small test program, but couldn't reproduce the
> issue with the backtrace.
>
> It's possible that the shortest way of reproducing this is for you to
> build the latest master branch of Emacs with the default compiler
> switches (which should yield -O2 -g3). If you go that way, let me
> know if you need help in actually forcing Emacs to fall through on the
> call to emacs_abort. I'd also be interested to know whether this is
> reproducible on GNU/Linux.
>
> This is with GCC 8.2.0, btw.
I'll give this a try.
I have GCC 8.3.1 and 9.0.1 readily available. Do you think it's
important to use 8.2.0 ?
Kevin
next prev parent reply other threads:[~2019-05-02 15:59 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-01 18:59 Eli Zaretskii
2019-05-01 20:17 ` Simon Marchi
2019-05-02 2:51 ` Kevin Buettner
2019-05-02 6:59 ` Eli Zaretskii
2019-05-02 7:26 ` Kevin Buettner
2019-05-02 15:27 ` Eli Zaretskii
2019-05-02 15:59 ` Kevin Buettner [this message]
2019-05-02 16:46 ` Eli Zaretskii
2019-05-02 18:08 ` Simon Marchi
2019-05-02 18:47 ` Eli Zaretskii
2019-05-02 18:55 ` Kevin Buettner
2019-05-02 19:32 ` Eli Zaretskii
2019-05-02 19:51 ` Kevin Buettner
2019-05-02 7:06 ` Eli Zaretskii
2019-05-02 7:38 ` Kevin Buettner
2019-05-02 15:23 ` Eli Zaretskii
2019-05-02 15:56 ` Kevin Buettner
2019-05-02 16:43 ` Eli Zaretskii
2019-05-02 18:25 ` Kevin Buettner
2019-05-02 18:52 ` Eli Zaretskii
2019-05-02 19:13 ` Kevin Buettner
2019-05-02 19:28 ` Eli Zaretskii
2019-05-02 19:45 ` Kevin Buettner
2019-05-02 19:56 ` Eli Zaretskii
2019-05-02 23:30 ` Kevin Buettner
2019-05-04 8:30 ` Eli Zaretskii
2019-05-05 20:04 ` Kevin Buettner
2019-05-06 15:33 ` Eli Zaretskii
2019-05-06 16:24 ` Kevin Buettner
2019-05-02 15:17 ` Eli Zaretskii
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=20190502085919.63b2d520@f29-4.lan \
--to=kevinb@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.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