public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "aburgess at redhat dot com" <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 08:10:00 +0000 [thread overview] Message-ID: <bug-22921-4717-YOayFYMYDN@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 #5 from Andrew Burgess <aburgess at redhat dot com> --- Created attachment 14677 --> https://sourceware.org/bugzilla/attachment.cgi?id=14677&action=edit Minimal reproducer Decompiled the shared library in the original reproducer, and created a new, minimal example of this issue, this time in source only. To use: tar -xf pr-22921.tar.xz cd pr-22921 make make debug The test should report FAILED. Then: make run The test, run outside GDB, should report PASSED. I haven't completely discounted that this might be a program error, but if it is, I can't see it yet. Also, when run under GDB the cmd_apb.gdb script is used. You'll notice inside it this line: ##delete which deletes all breakpoints. if this line is un-commented then the test, when run under GDB starts working again. So it does appear that the very presence of the software breakpoint causes the test to fail. I've done no additional debuggging of the issue so far. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-02-12 8:10 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 [this message] 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 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-YOayFYMYDN@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).