Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: asmwarrior <asmwarrior@gmail.com>
To: Keith Seitz <keiths@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA 1/3] Linespec rewrite: Parsing
Date: Sat, 24 Mar 2012 13:03:00 -0000	[thread overview]
Message-ID: <4F6DC651.6060704@gmail.com> (raw)
In-Reply-To: <4F67A319.4090608@redhat.com>

On 2012-3-20 5:20, Keith Seitz wrote:
> Hello,
>
> Let me again apologize for the size of this patch. Basically, this is
> going to be the "interesting" bits for reviewers. This patch is really
> huge. Bigger than linespec.c itself. Much of this is simply diff noise
> caused by some "new" functions looking too much like "old" functions and
> diff trying to be too clever.
>

I tried your patches under msys and mingw, and the result looks like break the existing mechanism, here is the log I try to set a bp in Codeblocks's source, but it failed :

[debug]> break "E:/code/cb/cb_trunk/src/plugins/codecompletion/parser/token.cpp:64"
[debug]unmatched quote

This command works OK before:

[debug]> break "E:/code/cb/cb_trunk/src/plugins/codecompletion/parser/token.cpp:64"
[debug]No source file named E:/code/cb/cb_trunk/src/plugins/codecompletion/parser/token.cpp.
[debug]Breakpoint 2 ("E:/code/cb/cb_trunk/src/plugins/codecompletion/parser/token.cpp:64) pending.

Yuanhui Zhang
Code::Blocks developer



  parent reply	other threads:[~2012-03-24 13:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-19 21:21 Keith Seitz
2012-03-20  3:56 ` Eli Zaretskii
2012-03-20  5:31   ` Keith Seitz
2012-03-20 17:26     ` Eli Zaretskii
2012-03-24 13:03 ` asmwarrior [this message]
2012-03-24 17:23   ` Keith Seitz
2012-03-25 12:27     ` asmwarrior
2012-03-26 13:23       ` asmwarrior
2012-03-25 12:28     ` asmwarrior
2012-03-26  0:40     ` Daniel Jacobowitz
2012-03-26 16:26       ` Tom Tromey
2012-03-26 18:52         ` Keith Seitz
2012-03-26 19:05       ` André Pönitz
2012-03-26 19:31 ` Tom Tromey
2012-03-26 20:36   ` Keith Seitz

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=4F6DC651.6060704@gmail.com \
    --to=asmwarrior@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=keiths@redhat.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