Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH][gdb/tdep] Detect get_pc_thunk call in i386 prologue
Date: Wed, 8 Jun 2022 11:13:31 +0200	[thread overview]
Message-ID: <64d3f391-f323-eaed-0504-927fde10fb7a@suse.de> (raw)
In-Reply-To: <20220530121003.GA16697@delia.home>

On 5/30/22 14:10, Tom de Vries wrote:
> Fix the regressions by updating the test-cases to accept the new output.

These regressions were those that I ran into with a first version of the 
patch, which handled only __x86.get_pc_thunk.ax.

This version handles bx and dx in addition, which triggers an additional 
regression (indeed another -O2 test-case):
...
FAIL: gdb.cp/step-and-next-inline.exp: no_header: not in inline 1
...

Anyway, a quick investigation shows that there are still more regs to 
handle:
...
$ objdump -d /lib/libc.so.6 | grep get_pc_thunk | awk '{print $9}' | sort -u

<__x86.get_pc_thunk.ax>
<__x86.get_pc_thunk.bp>
<__x86.get_pc_thunk.bx>
<__x86.get_pc_thunk.cx>
<__x86.get_pc_thunk.di>
<__x86.get_pc_thunk.dx>
<__x86.get_pc_thunk.si>
...
so with a more complete version of this patch, still more -O2 
regressions may show up.

Thanks,
- Tom

      reply	other threads:[~2022-06-08  9:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-30 12:10 Tom de Vries via Gdb-patches
2022-06-08  9:13 ` Tom de Vries via Gdb-patches [this message]

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=64d3f391-f323-eaed-0504-927fde10fb7a@suse.de \
    --to=gdb-patches@sourceware.org \
    --cc=tdevries@suse.de \
    /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