Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Xavier Roirand <roirand@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [RFA v4] enable/disable sub breakpoint range
Date: Mon, 23 Oct 2017 10:25:00 -0000	[thread overview]
Message-ID: <a8af4f4a-abac-be61-c6e8-3e039b5c1bac@redhat.com> (raw)
In-Reply-To: <c1310ac2-b958-f0b6-aabd-5f14f8524b79@adacore.com>

On 10/23/2017 11:07 AM, Xavier Roirand wrote:
> Hello,
> 
> Seems that my v3 patch sent in my previous email was not merging fine so
> here's a rebased version. Hope it will work better.
> 

Hmm, I still get (against current master / f6af9f3428fa):

$ patch --dry-run -i patch.diff -p1
checking file gdb/NEWS
checking file gdb/breakpoint.c
Hunk #1 FAILED at 93.
Hunk #2 FAILED at 14160.
Hunk #3 FAILED at 14178.
Hunk #4 FAILED at 14222.
Hunk #6 FAILED at 14287.
Hunk #7 FAILED at 14396.
6 out of 7 hunks FAILED
checking file gdb/doc/gdb.texinfo
checking file gdb/testsuite/gdb.cp/locbprange.cc
checking file gdb/testsuite/gdb.cp/locbprange.exp

Not sure why...  Does it work for you if you copy paste it from your
mail client?


There's a leading indentation in all lines in the commit log below which
suggests to me that you copy/pasted the patch from the output
of "git show"?  A better way is to use "git format-patch -1" instead.
That makes it possible to use "git am" to import a patch.
Please can you try that, and send the result as an attachment.

[Please also look into git send-email for the future.  It should
make things smoother.  Joel uses that so I assume it wouldn't be
a problem on your server's end.]

> -----
> 
>     Allow enabling/disabling breakpoint location range
> 
>     In some cases, adding one breakpoint corresponds to multiple
>     places in a program thus leads GDB to define main breakpoint
>     number and other breakpoints using location number with syntax:
> 

...

Thanks,
Pedro Alves


  parent reply	other threads:[~2017-10-23 10:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-03 10:26 [RFA v3] " Xavier Roirand
2017-10-03 14:50 ` Eli Zaretskii
2017-10-03 16:02   ` Pedro Alves
2017-10-03 16:05     ` Pedro Alves
2017-10-03 16:06     ` Xavier Roirand
2017-10-03 16:34     ` Eli Zaretskii
2017-10-03 16:40       ` Pedro Alves
2017-10-03 17:00         ` Eli Zaretskii
2017-10-03 17:15           ` Pedro Alves
2017-10-03 18:32             ` Eli Zaretskii
2017-10-06  8:54     ` Xavier Roirand
2017-10-16 22:21       ` Philippe Waroquiers
2017-10-20 12:17     ` Xavier Roirand
2017-10-20 14:41       ` Pedro Alves
2017-10-20 14:58         ` Pedro Alves
     [not found]           ` <c1310ac2-b958-f0b6-aabd-5f14f8524b79@adacore.com>
2017-10-23 10:25             ` Pedro Alves [this message]
2017-10-23 11:07               ` [RFA v4] " Xavier Roirand
2017-10-26 13:11                 ` Pedro Alves

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=a8af4f4a-abac-be61-c6e8-3e039b5c1bac@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=roirand@adacore.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