From: "Metzger, Markus T" <markus.t.metzger@intel.com>
To: Guinevere Larsen <blarsen@redhat.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH v4 4/4] gdb, infrun: fix multi-threaded reverse stepping
Date: Tue, 9 Apr 2024 09:14:08 +0000 [thread overview]
Message-ID: <DM8PR11MB5749D52F7079E5F2E32E596FDE072@DM8PR11MB5749.namprd11.prod.outlook.com> (raw)
In-Reply-To: <1fd4d2e8-cf01-409c-ba83-dd311b608726@redhat.com>
>I'm slowly making my way through this series, but this patch
>specifically seems to not apply at all. Trying to use git am --3way
>gives me the following output:
>
>Applying: gdb, infrun: fix multi-threaded reverse stepping
>error: sha1 information is lacking or useless (gdb/infrun.c).
>error: could not build fake ancestor
>Patch failed at 0001 gdb, infrun: fix multi-threaded reverse stepping
That is very strange. I just did a 'git pull --rebase' without problems.
I also tried 'git am' on the patches I had sent out. They do not apply
cleanly on current master but when I reset to an older commit, they
do apply cleanly.
I can try sending the version with the nit fixed rebased on current master.
Markus.
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de>
Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
prev parent reply other threads:[~2024-04-09 9:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 11:34 [PATCH v4 0/4] btrace: infrun fixes Markus Metzger
2024-03-12 11:34 ` [PATCH v4 1/4] gdb, infrun, btrace: fix reverse/replay stepping at end of execution history Markus Metzger
2024-03-12 11:56 ` Hannes Domani
2024-03-13 11:47 ` Hannes Domani
2024-04-04 18:03 ` Guinevere Larsen
2024-04-05 9:12 ` Metzger, Markus T
2024-04-05 12:53 ` Guinevere Larsen
2024-03-12 11:34 ` [PATCH v4 2/4] gdb, infrun, record: fix hang when step-over fails with no-history Markus Metzger
2024-04-04 18:27 ` Guinevere Larsen
2024-03-12 11:34 ` [PATCH v4 3/4] gdb, infrun, record: move no-history notification into normal_stop Markus Metzger
2024-04-04 18:57 ` Guinevere Larsen
2024-04-05 9:16 ` Metzger, Markus T
2024-04-05 15:51 ` Guinevere Larsen
2024-03-12 11:34 ` [PATCH v4 4/4] gdb, infrun: fix multi-threaded reverse stepping Markus Metzger
2024-04-03 20:27 ` Guinevere Larsen
2024-04-09 9:14 ` Metzger, Markus T [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=DM8PR11MB5749D52F7079E5F2E32E596FDE072@DM8PR11MB5749.namprd11.prod.outlook.com \
--to=markus.t.metzger@intel.com \
--cc=blarsen@redhat.com \
--cc=gdb-patches@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).