public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Bob Rossi <bob@brasko.net>
Cc: gdb@sourceware.org
Subject: Re: annotation issue with newer gdb's?
Date: Mon, 6 Apr 2020 11:46:47 -0700	[thread overview]
Message-ID: <20200406184647.GA25518@adacore.com> (raw)
In-Reply-To: <20200404233339.GA5321@xubuntu.brasko.net>

> In older versions of gdb (at least until 7.11 which i'm using and
> possibly later) I see the following behavior when starting gdb and
> typing, 'b main'
> 
>     "\r\n\032\032post-prompt\r\n"
>     "Breakpoint 1 at 0x4006c0: file test.cpp, line 42.\r\n"
>     "\r\n\032\032breakpoints-invalid\r\n"
> 
> In GDB 9.1, I'm see the following,
> 
>     "\r\n\032\032post-prompt\r\n"
>     "\r\nBreakpoint 1 at \033[34m0x4006c0\033[m: file \033[32mtest.cpp\033[m, line 42."
>     "\r\n\032\032breakpoints-invalid\r\n"
> 
> You can see that the newline moved on the "Breakpoint 1" line
> from the end of the line (in older versions) to the beginning of the
> line (in newer versions).
> 
> This ultimately caused CGDB to misbehave.
> 
> Correctly working CGDB,
>     Reading symbols from ./main...done.
>     (gdb) b main
>     Breakpoint 1 at 0x4006c0: file test.cpp, line 42.
>     (gdb) 
> 
> Incorrectly working CGDB,
>     Reading symbols from ./main...
>     (gdb) b main
> 
>     Breakpoint 1 at 0x4006c0: file test.cpp, line 42.(gdb) 
> 
> Was this change to the annotations made on purpose?

I haven't followed development much, lately ( :-( ), but I don't
think so. This looks similer to:

https://sourceware.org/bugzilla/show_bug.cgi?id=25190

That particular PR is reported as being fixed for 9.1, so it's
not the same problem, or the fix was incomplete.

Have you tried master, by any chance?

-- 
Joel

  reply	other threads:[~2020-04-06 18:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-04 23:33 Bob Rossi
2020-04-06 18:46 ` Joel Brobecker [this message]
2020-04-15  2:00   ` Bob Rossi

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=20200406184647.GA25518@adacore.com \
    --to=brobecker@adacore.com \
    --cc=bob@brasko.net \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).