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 07:35:15 +0000	[thread overview]
Message-ID: <bug-22921-4717-rCxsIq177M@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 #4 from Stas Sergeev <stsp at users dot sourceforge.net> ---
(In reply to Andrew Burgess from comment #3)
> I know this is a long shot on such an old bug, but the tar file includes a
> pre-compiled libfdpp.so library, but not the source to reproduce it.  Could
> that source be made available?

Sources of libfdpp are of course available on github,
but they have changed a lot in 5 years, plus I think
I added an extra hacks there for the sake of this test-suit.
All that is involved from libfdpp here, is a plt entry.
Do you really think the sources will help?
If you want, I can try to reduce this test-case even
more, use the custom lib instead of libfdpp and so on.
But will this help, if all we need is plt?
Is there something particular you want to see from
the source of libfdpp?
The wrapper that sets up SIGALRM and does dlopen(), is
included in a source form and I was quite confident this
is all we need, no?

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

  parent reply	other threads:[~2023-02-12  7:35 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 [this message]
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
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-rCxsIq177M@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).