From: Zied Guermazi <zied.guermazi@trande.de>
To: Simon Marchi <simon.marchi@polymtl.ca>, gdb-patches@sourceware.org
Subject: Re: [PATCH v3 0/7] extend branch tracing to use ARM CoreSight traces
Date: Mon, 5 Apr 2021 09:38:49 +0200 [thread overview]
Message-ID: <f6586281-e7cd-3ee4-0108-544d94c3ebbd@trande.de> (raw)
In-Reply-To: <9abf7597-acf3-bcea-8d29-a961fe75d238@polymtl.ca>
hi Simon,
the first error message looks related to the change log.
I am adding the change logs manually to the mail, is this fine? how
shall the change logs be provided? shall I change the ChangeLog files
located under gdb, gdbserver and gdbsupport folder? is it enough to put
the change logs in the mail header?
Kind Regards
Zied
On 05.04.21 02:09, Simon Marchi wrote:
> On 2021-04-02 12:05 p.m., Zied Guermazi wrote:
>> hi Simon
>>
>> the patchset applies to this commit
>>
>> commit 39b07596938e4c2a7251d77ea01981d475747599 (*origin/master*, *origin/HEAD*, *master*)
>> Author: GDB Administrator <gdbadmin@sourceware.org>
>> Date: Thu Feb 25 00:00:20 2021 +0000
>>
>> Automatic date update in version.in
>>
>> Kind Regards
>> Zied Guermazi
> Hmm, so I get this when applying patch 2:
>
>
> $ git am -3 ~/patches/\[PATCH\ v3\ 2_7\]\ add\ btrace\ coresight\ related\ commands.eml
> Applying: add btrace coresight related commands
> Using index info to reconstruct a base tree...
> /home/simark/src/binutils-gdb/.git/worktrees/avr/rebase-apply/patch:394: trailing whitespace.
> * btrace-common.h (btrace_format): add BTRACE_FORMAT_ETM
> error: patch failed: gdb/record-btrace.c:2950
> error: gdb/record-btrace.c: patch does not apply
> error: patch failed: gdbsupport/btrace-common.cc:36
> error: gdbsupport/btrace-common.cc: patch does not apply
> error: Did you hand edit your patch?
> It does not apply to blobs recorded in its index.
> Patch failed at 0001 add btrace coresight related commands
> hint: Use 'git am --show-current-patch=diff' to see the failed patch
> When you have resolved this problem, run "git am --continue".
> If you prefer to skip this patch, run "git am --skip" instead.
> To restore the original branch and stop patching, run "git am --abort".
>
> Are you able to successfully apply the patches from the mail?
>
> Simon
next prev parent reply other threads:[~2021-04-05 7:38 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 2:52 Zied Guermazi
2021-03-31 2:52 ` [PATCH v3 1/7] configure gdb build system for supporting btrace on arm processors Zied Guermazi
2021-03-31 2:52 ` [PATCH v3 2/7] add btrace coresight related commands Zied Guermazi
2021-03-31 6:32 ` Eli Zaretskii
2021-03-31 18:30 ` Luis Machado
2021-03-31 20:24 ` Zied Guermazi
2021-04-01 16:11 ` Luis Machado
2021-03-31 2:52 ` [PATCH v3 3/7] start/stop btrace with coresight etm and parse etm buffer. nat independant Zied Guermazi
2021-03-31 20:23 ` Luis Machado
[not found] ` <a78174f9-177f-3757-6b33-d09f38f1fec8@trande.de>
2021-04-01 21:04 ` Zied Guermazi
2021-03-31 2:52 ` [PATCH v3 4/7] start/stop btrace with coresight etm and collect etm buffer on linux os Zied Guermazi
2021-04-01 12:16 ` Luis Machado
2021-04-01 21:57 ` Zied Guermazi
2021-03-31 2:52 ` [PATCH v3 5/7] fix issue: gdb hangs in the command following a commad returning with TARGET_WAITKIND_NO_HISTORY Zied Guermazi
2021-04-01 12:18 ` Luis Machado
2021-03-31 2:52 ` [PATCH v3 6/7] add support for coresight btrace via remote protocol Zied Guermazi
2021-03-31 6:33 ` Eli Zaretskii
2021-04-01 12:45 ` Luis Machado
2021-04-01 22:58 ` Zied Guermazi
2021-03-31 2:52 ` [PATCH v3 7/7] adapt btrace testcases for arm target Zied Guermazi
2021-04-01 13:34 ` Luis Machado
2021-04-04 19:30 ` Zied Guermazi
2021-04-06 13:09 ` Luis Machado
2021-04-09 19:34 ` Zied Guermazi
2021-04-12 17:11 ` Luis Machado
2021-04-02 16:02 ` [PATCH v3 0/7] extend branch tracing to use ARM CoreSight traces Simon Marchi
2021-04-02 16:05 ` Zied Guermazi
2021-04-05 0:09 ` Simon Marchi
2021-04-05 7:38 ` Zied Guermazi [this message]
2021-04-06 16:25 ` Simon Marchi
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=f6586281-e7cd-3ee4-0108-544d94c3ebbd@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).