From: Zied Guermazi <zied.guermazi@trande.de>
To: Simon Marchi <simon.marchi@polymtl.ca>, gdb-patches@sourceware.org
Subject: Re: [PATCH v4 1/7] configure gdb build system for supporting btrace on arm processors
Date: Sun, 11 Apr 2021 02:35:37 +0200 [thread overview]
Message-ID: <79649a10-51be-5937-bdd5-7ecf0d25fc9f@trande.de> (raw)
In-Reply-To: <94e91d0a-5d36-c2e0-5a7d-012b950e5b1c@polymtl.ca>
hi Simon
this patch set was generated using the command "git format-patch
--cover-letter -7".
the patch set was edited manually to add the mail body up to the three
dashes "---".
it was then send using the command "git send-email *.patch".
is this the right procedure for generating and distributing it?
/Zied
On 11.04.21 00:40, Simon Marchi wrote:
> On 2021-04-10 5:17 p.m., Zied Guermazi wrote:> This patch adds the possibility to build GDB with support for branch tracing
>> using ARM CoreSight traces.
>> New flag is --with-arm-cs
>>
>> gdb/ChangeLog
>>
>> * Makefile.in LIBOPENCSD_C_API: Regenerated.
>> * config.in LIBOPENCSD_C_API: Regenerated.
>> * configure: Regenerated.
>> * configure.nat: add nat/linux-btrace.o to the build
>> for aarch64 and arm
>> * top.c (print_gdb_configuration): add --with-arm-cs
>> or --without-arm-cs according to the configuration.
>>
>> gdbserver/ChangeLog
>> * gdbserver/configure: Regenerated.
>> * gdbserver/config.in: Regenerated.
>>
>> gdbsupport/ChangeLog
>>
>> * gdbsupport/common.m4: check --with-arm-cs configuration
>> flag, perf_event and opencsd_c_api to set compilation flags.
>> * gdbsupport/config.in: Regenerated.
>> * gdbsupport/Makefile.in: Regenerated.
>> * gdbsupport/configure: Regenerated.
> Hi Zied,
>
> I am puzzled, I still have problem applying your patches:
>
>
> $ git am ~/patches/\[PATCH\ v4\ 1_7\]\ configure\ gdb\ build\ system\ for\ supporting\ btrace\ on\ arm\ processors\ -\ Zied\ Guermazi\ \<zied.guermazi@trande.de\>\ -\ 2021-04-10\ 1717.eml
> Applying: configure gdb build system for supporting btrace on arm processors
> error: patch failed: gdb/configure.nat:235
> error: gdb/configure.nat: patch does not apply
>
> Simon
This message is intended only for the use of the named recipient(s) and
may contain confidential and/or privileged information. If you are not
the intended recipient, please contact the sender and delete the
message. Any unauthorized use of the information contained in this
message is prohibited.
next prev parent reply other threads:[~2021-04-11 0:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-10 21:17 [PATCH v4 0/7] extend branch tracing to use ARM CoreSight traces Zied Guermazi
2021-04-10 21:17 ` [PATCH v4 1/7] configure gdb build system for supporting btrace on arm processors Zied Guermazi
2021-04-10 22:40 ` Simon Marchi
2021-04-11 0:35 ` Zied Guermazi [this message]
2021-04-11 1:09 ` Simon Marchi
2021-04-11 1:14 ` Zied Guermazi
2021-04-11 1:45 ` simon.marchi
2021-04-10 21:17 ` [PATCH v4 2/7] add btrace coresight related commands Zied Guermazi
2021-04-11 6:41 ` Eli Zaretskii
2021-04-10 21:17 ` [PATCH v4 3/7] start/stop btrace with coresight etm and parse etm buffer. nat independant Zied Guermazi
2021-04-10 21:17 ` [PATCH v4 4/7] start/stop btrace with coresight etm and collect etm buffer on linux os Zied Guermazi
2021-04-10 21:17 ` [PATCH v4 5/7] fix issue: gdb hangs in the command following a commad returning with TARGET_WAITKIND_NO_HISTORY Zied Guermazi
2021-04-10 21:17 ` [PATCH v4 6/7] add support for coresight btrace via remote protocol Zied Guermazi
2021-04-11 6:43 ` Eli Zaretskii
2021-04-10 21:17 ` [PATCH v4 7/7] adapt btrace testcases for arm target Zied Guermazi
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=79649a10-51be-5937-bdd5-7ecf0d25fc9f@trande.de \
--to=zied.guermazi@trande.de \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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).