From: Timur Golubovich <timurgol007@gmail.com>
To: Guinevere Larsen <guinevere@redhat.com>
Cc: "Aktemur, Tankut Baris" <tankut.baris.aktemur@intel.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Andrew Burgess <aburgess@redhat.com>
Subject: Re: [PATCH v8] This commit adds record full support for rv64gc instruction set
Date: Wed, 23 Apr 2025 17:39:50 +0300 [thread overview]
Message-ID: <CADR_JzAALf=iTQR1ZrVV447JzG=B6RPtz_81WPOcnFP-P2FpOg@mail.gmail.com> (raw)
In-Reply-To: <27ac9bfa-7738-4601-8cf8-a2d0582db90f@redhat.com>
Hi!
Thanks for the quick fix. That was a great review, good job.
I'd be happy to continue working on gdb.
>
> On 4/23/25 11:01 AM, Aktemur, Tankut Baris wrote:
> > On Wednesday, April 23, 2025 2:14 PM, Guinevere Larsen wrote:
> >> Hi! Sorry for the delay, I'm applying and fixing merge conflicts, and
> >> will be pushing this patch soon!
> >>
> >> If you plan on continue to develop GDB, you may want to get in contact
> >> with Tom Tromey to setup write-after-approval access, so you are able to
> >> push your own patches :)
> >>
> >> --
> >> Cheers,
> >> Guinevere Larsen
> >> She/Her/Hers
> >>
> >> On 4/22/25 2:36 PM, Timur Golubovich wrote:
> >>> Hi!
> >>> Sorry to bother, but It seems like no one else has any questions about
> >>> this patch.
> >>> Maybe then it's possible to merge it?
> > Hello Guinevere, Timur,
> >
> > With this patch, I started getting
> >
> > /usr/bin/ld: riscv-linux-tdep.o: in function `riscv_linux_syscall_record(regcache*, unsigned long)':
> > /user/taktemur/gdb/gdb/riscv-linux-tdep.c:230: undefined reference to `riscv64_canonicalize_syscall(int)'
> >
> > I had configured GDB with --enable-targets=all.
> Oh, oops. the riscv-canonicalize-syscall.c file hasn't been added to the
> makefile, so all targets fails. I'm fixing this and the other build
> issue (a commit from Tromey slightly changing one gdb syscall name) and
> pushing the fix asap
>
> --
> Cheers,
> Guinevere Larsen
> She/Her/Hers
>
prev parent reply other threads:[~2025-04-23 14:40 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 22:26 [PATCH] gdb/riscv: Add record support for rv64gc instructions Timur
2024-11-18 19:46 ` Guinevere Larsen
2024-11-26 14:17 ` [PATCH v2] " Timur
2024-11-27 14:23 ` Guinevere Larsen
2024-12-03 18:30 ` [PATCH v3] " Timur
2024-12-13 18:10 ` Guinevere Larsen
2024-12-17 0:10 ` [PATCH v4] This commit adds record full support for rv64gc instruction set Timur
2024-12-17 14:23 ` Guinevere Larsen
2024-12-23 15:12 ` [PATCH v5] " Timur
2024-12-23 18:55 ` Guinevere Larsen
2024-12-31 16:09 ` [PATCH v6] " Timur
2025-01-10 18:12 ` Guinevere Larsen
2025-01-16 15:48 ` [PATCH v7] " Timur
2025-02-10 18:07 ` [PING][PATCH v8] " Timur
2025-02-10 19:30 ` Eli Zaretskii
2025-02-11 22:06 ` [PATCH] " Timur
2025-02-26 11:14 ` [PATCH][PING] " Timur
2025-03-13 10:38 ` Andrew Burgess
2025-03-13 15:03 ` [PATCH] " Andrew Burgess
2025-03-18 18:49 ` [PATCH v8] " Timur
2025-03-31 17:50 ` [PING][PATCH] " Timur
2025-04-08 12:33 ` Timur Golubovich
2025-04-10 9:16 ` Andrew Burgess
2025-04-10 9:16 ` [PATCH v8] " Andrew Burgess
2025-04-10 11:55 ` Timur
2025-04-14 7:40 ` Andrew Burgess
2025-04-14 8:44 ` Timur Golubovich
2025-04-14 12:03 ` Guinevere Larsen
2025-04-22 17:36 ` Timur Golubovich
2025-04-23 12:13 ` Guinevere Larsen
2025-04-23 14:01 ` Aktemur, Tankut Baris
2025-04-23 14:13 ` Guinevere Larsen
2025-04-23 14:39 ` Timur Golubovich [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='CADR_JzAALf=iTQR1ZrVV447JzG=B6RPtz_81WPOcnFP-P2FpOg@mail.gmail.com' \
--to=timurgol007@gmail.com \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=guinevere@redhat.com \
--cc=tankut.baris.aktemur@intel.com \
/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