From: Bob Rossi <bob@brasko.net>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: gdb@sourceware.org, Marc Khouzam <marc.khouzam@ericsson.com>,
Pedro Alves <palves@redhat.com>
Subject: Re: source annotation now prints source line
Date: Sat, 13 Mar 2021 12:01:21 -0500 [thread overview]
Message-ID: <20210313170028.GA7813@xubuntu.brasko.net> (raw)
In-Reply-To: <20200416174128.GA1633140@embecosm.com>
On Thu, Apr 16, 2020 at 06:41:28PM +0100, Andrew Burgess wrote:
> I'll take a look to see if there's a good way to give you the
> functionality you're looking for and close the bugs off.
Thank you for doing this Andrew, I appreciate it.
Ironically, I just upgraded CGDB to no longer use annotations.
I'm moved it from annotations to gdb/mi, in the same way that
Eclipse uses MI, by using the new-ui feature of gdb. Now i see the
source linse are still visible in the console. gdb doesn't know
to not show them in this mode.
To recap,
- cgdb using annotations does not show code in console
- cgdb using mi using new-ui does show code in console
- gdb tui does not show code in console
- eclipse probably shows code in console, as it uses mi and new-ui
Would it be to much to ask that if new-ui is being used, that we
assume a front end is being used, and not display the code in the console?
I've CC'd Pedro and Marc as I believe they may be the relevant people to
have an opinion on how this would impact eclipse.
Thanks,
Bob Rossi
next prev parent reply other threads:[~2021-03-13 17:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-04 23:54 Bob Rossi
2020-04-14 11:23 ` Bob Rossi
2020-04-14 12:17 ` Andrew Burgess
2020-04-14 12:57 ` Andrew Burgess
2020-04-15 2:13 ` Bob Rossi
2020-04-16 17:41 ` Andrew Burgess
2021-03-13 17:01 ` Bob Rossi [this message]
2021-03-15 13:10 ` Pedro Alves via Gdb
2024-05-04 20:09 ` Robert Rossi
2024-05-05 15:36 ` Robert Rossi
2024-05-05 16:06 ` Eli Zaretskii via Gdb
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=20210313170028.GA7813@xubuntu.brasko.net \
--to=bob@brasko.net \
--cc=andrew.burgess@embecosm.com \
--cc=gdb@sourceware.org \
--cc=marc.khouzam@ericsson.com \
--cc=palves@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