From: asmwarrior <asmwarrior@gmail.com>
To: gdb@sourceware.org
Subject: Re: [mingw,gdb CVS HEAD] can't set breakpoint
Date: Fri, 27 Jul 2012 05:02:00 -0000 [thread overview]
Message-ID: <501220C2.5010509@gmail.com> (raw)
In-Reply-To: <50121332.6010901@gmail.com>
On 2012-7-27 12:04, asmwarrior wrote:
> I just see this message: (when debugging under Code::Blocks)
>
> [debug]> break "E:/code/cb/test_code/Toggle/MyWXMain.cpp:66"
> [debug]Function "66" not defined in "E:/code/cb/test_code/Toggle/MyWXMain.cpp".
> [debug]Breakpoint 2 ("E:/code/cb/test_code/Toggle/MyWXMain.cpp:66") pending.
>
> Why this command is regard as "Function 66".
> When the app started, it can't hit the bp.
>
> It works OK with gdb cvs 2012-07-25.
>
> Yuanhui Zhang
>
>
I believe this issue is caused by the last two commits in file "linespec.c".
Revision: 5134bbd001531c5c6d02573d4d7fb86b17a549ec
Author: Keith Seitz
Date: 2012-7-27 0:22:44
Message:
* linespec.c (linespec_lexer_lex_number): The input
is also a valid number if the next character is a comma
or colon.
----
Modified: gdb/ChangeLog
Modified: gdb/linespec.c
and
Revision: 4643fc6023b9d9aad57359b5624756b880c085d1
Author: Hui Zhu
Date: 2012-7-25 20:26:23
Message:
2012-07-25 Hui Zhu <hui_zhu@mentor.com>
* linespec.c (linespec_lexer_lex_number): Update comments,
change the return and add check to make sure the input is
the decimal numbers.
(linespec_lexer_lex_one): If linespec_lexer_lex_number return
false, call linespec_lexer_lex_string.
----
Modified: gdb/ChangeLog
Modified: gdb/linespec.c
I revert these two changes, and the breakpoint command works OK.
next prev parent reply other threads:[~2012-07-27 5:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 4:04 asmwarrior
2012-07-27 5:02 ` asmwarrior [this message]
2012-07-29 19:01 ` 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=501220C2.5010509@gmail.com \
--to=asmwarrior@gmail.com \
--cc=gdb@sourceware.org \
/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