From: Brother Josef <thykeeper@nerdshack.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sourceware.org
Subject: Re: Controlling gdb outside the terminal
Date: Fri, 07 Sep 2007 11:18:00 -0000 [thread overview]
Message-ID: <66804A1A-5EC3-408A-AB67-64BE24EEAA67@nerdshack.com> (raw)
In-Reply-To: <20070907015455.GA23872@caradoc.them.org>
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
On Sep 7, 2007, at 8:54 AM, Daniel Jacobowitz wrote:
> On Fri, Sep 07, 2007 at 08:12:55AM +0700, Brother Josef wrote:
>> I have a small amount of UNIX knowledge but have been using the
>> gdb on the
>> command line and decided it would be possible to make a GUI to
>> debug Pascal
>> under Mac OS X. With my limited knowledge I found that calls to
>> popen and
>> reading the stream would work to with most commands but gdb
>> complains "gdb)
>> Exception condition detected on fd 0 error detected on stdin". gpd
>> runs a
>> seperate process so I think I need to be sending commands to that
>> pid but I
>> just can't figure it out. Could anyone point me to some
>> informations? thanks
>> for your time.
>
> You need to read up on pseudo-terminals and job control for Unix
> systems. However, I don't think you will need to if you use GDB
> in MI mode; that is highly recommended for front ends.
>
> --
> Daniel Jacobowitz
> CodeSourcery
Regards,
Josef
next prev parent reply other threads:[~2007-09-07 10:59 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 [this message]
2007-09-07 11:46 ` 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=66804A1A-5EC3-408A-AB67-64BE24EEAA67@nerdshack.com \
--to=thykeeper@nerdshack.com \
--cc=drow@false.org \
--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