public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "stsp at users dot sourceforge.net" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/22921] breakpoint in PLT corrupts function argument in $rcx
Date: Sun, 12 Feb 2023 15:38:49 +0000	[thread overview]
Message-ID: <bug-22921-4717-usiUvmmsQW@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-22921-4717@http.sourceware.org/bugzilla/>

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

--- Comment #12 from Stas Sergeev <stsp at users dot sourceforge.net> ---
So you are really at it, that's cool! :)
Not that I can use your new test-case, as it now works like this:

Program received signal SIGALRM, Alarm clock.
[displaced] displaced_step_prepare_throw: displaced-stepping 2910780.2910780.0
now
[displaced] prepare: selected buffer at 0x5555555550c2
[displaced] prepare: saved 0x5555555550c2: 1e fa 31 ed 49 89 d1 5e 48 89 e2 48
83 e4 f0 50
[displaced] amd64_displaced_step_copy_insn: copy
0x7ffff7fbb0d0->0x5555555550c2: f3 0f 1e fa f2 ff 25 45 2f 00 00 0f 1f 44 00 00
[displaced] displaced_step_prepare_throw: prepared successfully
thread=2910780.2910780.0, original_pc=0x7ffff7fbb0d0,
displaced_pc=0x5555555550c2
[displaced] resume_1: run 0x5555555550c2: f3 0f 1e fa
[displaced] finish: restored 2910780.2910780.0 0x5555555550c2
[displaced] amd64_displaced_step_fixup: fixup (0x7ffff7fbb0d0, 0x5555555550c2),
insn = 0xf3 0x0f ...
[displaced] amd64_displaced_step_fixup: relocated %rip from 0x5555555550c6 to
0x7ffff7fbb0d4
PASSED

Breakpoint 1, breakpt () at tst2.cc:18
18      }
1: x/i $pc
=> 0x5555555551de <_Z7breakptv+8>:      nop
2: /x $rcx = 0x7ffff7d0cd94
(gdb) 

And falls inside the gdb prompt, with "PASSED" already written...
But I guess I'll just try my own test-case on an already fixed
gdb some time later. :)

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

  parent reply	other threads:[~2023-02-12 15:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-22921-4717@http.sourceware.org/bugzilla/>
2023-02-12  6:57 ` aburgess at redhat dot com
2023-02-12  7:35 ` stsp at users dot sourceforge.net
2023-02-12  8:10 ` aburgess at redhat dot com
2023-02-12  8:17 ` stsp at users dot sourceforge.net
2023-02-12 10:17 ` stsp at users dot sourceforge.net
2023-02-12 10:20 ` stsp at users dot sourceforge.net
2023-02-12 15:26 ` aburgess at redhat dot com
2023-02-12 15:27 ` aburgess at redhat dot com
2023-02-12 15:32 ` aburgess at redhat dot com
2023-02-12 15:38 ` stsp at users dot sourceforge.net [this message]
2023-02-28 15:03 ` aburgess at redhat dot com
2023-04-06 13:27 ` cvs-commit at gcc dot gnu.org
2023-04-06 13:29 ` aburgess at redhat 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-22921-4717-usiUvmmsQW@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).