From: Bob Rossi <bob_rossi@cox.net>
To: Brother Josef <thykeeper@nerdshack.com>
Cc: Daniel Jacobowitz <drow@false.org>, gdb@sourceware.org
Subject: Re: Controlling gdb outside the terminal
Date: Fri, 07 Sep 2007 11:46:00 -0000 [thread overview]
Message-ID: <20070907111751.GI5805@cox.net> (raw)
In-Reply-To: <66804A1A-5EC3-408A-AB67-64BE24EEAA67@nerdshack.com>
On Fri, Sep 07, 2007 at 05:54:40PM +0700, Brother Josef wrote:
> excellent, thank you. and yes actually I do need to look into MI
> mode, I'm new to GDB and just now considering it as the future in how
> I might be debugging. Could I run GDB without that error and continue
> to write and read from the program from within my Mac app?
>
> Could anyone point me to any source code on pseudo-terminals or
> documents? I have been looking around today and I still can't get a
> clear picture of how such code would look providing I could even
> write it. ;) thanks again
Here is a gdb/mi parser.
http://cgdb.svn.sourceforge.net/viewvc/cgdb/cgdb/trunk/lib/gdbmi/
I would start out using that. I currently have not used this parser in a
production front end yet, however, I expect to do this soon, especially
since my push parser patch is finally complete in bison. That means I
can convert the parser to being completely non blocking.
It is capable of parsing all of the mi commands that the gdb testsuite
outputs.
Here is the code I use to open a pseudo terminal,
http://cgdb.svn.sourceforge.net/viewvc/cgdb/cgdb/trunk/various/util/include/pseudo.h?view=log
http://cgdb.svn.sourceforge.net/viewvc/cgdb/cgdb/trunk/various/util/src/pseudo.c?view=log
Enjoy,
Bob Rossi
prev parent reply other threads:[~2007-09-07 11:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-07 1:33 Brother Josef
[not found] ` <20070907015455.GA23872@caradoc.them.org>
2007-09-07 11:18 ` Brother Josef
2007-09-07 11:46 ` Bob Rossi [this message]
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=20070907111751.GI5805@cox.net \
--to=bob_rossi@cox.net \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
--cc=thykeeper@nerdshack.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