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 10:17:08 +0000 [thread overview] Message-ID: <bug-22921-4717-E1My3gYqgl@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-22921-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=22921 Stas Sergeev <stsp at users dot sourceforge.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #10865|0 |1 is obsolete| | --- Comment #7 from Stas Sergeev <stsp at users dot sourceforge.net> --- Created attachment 14678 --> https://sourceware.org/bugzilla/attachment.cgi?id=14678&action=edit test case I checkouted the old sources from git and did the minimal reproducer because yours doesn't work for me. Unfortunately I couldn't get rid of the large C++ header, because if that func returns something other than the object it does return now, the reproducer stops working. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-02-12 10:17 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 [this message] 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 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-E1My3gYqgl@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: linkBe 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).