[PATCH v3 0/7] extend branch tracing to use ARM CoreSight traces

[Zied Guermazi]

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