Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Bob Rossi <bob@brasko.net>, Simon Marchi <simon.marchi@polymtl.ca>
Cc: Marc Khouzam <marc.khouzam@ericsson.com>, gdb@sourceware.org
Subject: Re: GDB/MI questions
Date: Thu, 19 Jan 2017 16:33:00 -0000	[thread overview]
Message-ID: <d647c512-1fbd-6b28-cec0-9f417ea6102e@redhat.com> (raw)
In-Reply-To: <20170119162704.GE6289@xubuntu.brasko.net>

On 01/19/2017 04:27 PM, Bob Rossi wrote:
>>> I might give that a try. However, since CGDB already has great terminal
>>> emulation, it's not a huge deal. The other downside is, CGDB works with
>>> lots of GDB's. Using this feature leaves behind many GDBs. Or I'd have
>>> to support two modes. Yuck.
>>
>> You are right, that's the downside of newer stuff...
> 
> I'll have to check out this new functionality...

As first step, I'd suggest starting by experimenting with
starting gdb outside cgdb, manually, on the "normal" command line,
using the command Marc showed.  With a few hacks I suspect you'd
be able to make it work quickly.  You may even want to enable that
as supported use case.  If/when cgdb works with that,
then the rest is largely a "GUI" problem.  I.e., make the
frontend's console window a terminal emulator, and make cgdb
start gdb with I/O redirected there.  There are probably
libraries out there one can reuse for that.

Thanks,
Pedro Alves


  reply	other threads:[~2017-01-19 16:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170119031445.GA24616@xubuntu.brasko.net>
2017-01-19 14:31 ` Marc Khouzam
2017-01-19 14:52   ` Bob Rossi
2017-01-19 15:06     ` Pedro Alves
2017-01-19 15:11   ` Bob Rossi
2017-01-19 15:24     ` Marc Khouzam
2017-01-19 15:40       ` Jan Vrany
2017-01-19 16:17         ` Pedro Alves
2017-01-19 15:47     ` Simon Marchi
2017-01-19 16:03       ` Bob Rossi
2017-01-19 16:15         ` Simon Marchi
2017-01-19 16:27           ` Bob Rossi
2017-01-19 16:33             ` Pedro Alves [this message]
2017-01-19 14:43 ` 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=d647c512-1fbd-6b28-cec0-9f417ea6102e@redhat.com \
    --to=palves@redhat.com \
    --cc=bob@brasko.net \
    --cc=gdb@sourceware.org \
    --cc=marc.khouzam@ericsson.com \
    --cc=simon.marchi@polymtl.ca \
    /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