public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: "Nimesh D Chanchani" <nimeshc@rediffmail.com>
To: gdb@sources.redhat.com
Subject: I/O mechanism in libGDB
Date: Sun, 09 Mar 2003 11:24:00 -0000	[thread overview]
Message-ID: <20030309112417.12639.qmail@webmail25.rediffmail.com> (raw)

Hi,

I found your id from google groups. Thank god i found it.
well... I am required to upgrade gdb implementation 4.17 for zsp

processor to libGDB implementation for GDB 5.2.

I was going through API specification of libGDB in the one of the 
only

2 documents available on the web.

http://www.cs.utah.edu/dept/old/texinfo/libgdb/libgdb_toc.html#SEC4

I had some queries about the i/o mechanism used in libGDB .

what my understanding is that when for example the GDB gives the

information on the terminal about (say)  a recently created 
break

point, it would have to be parsed by a libGDB API function and 
give it

to the GUI in a "STANDARD FORMAT" irrespective of the version of 
GDB

being used.

for this the document

http://www.cs.utah.edu/dept/old/texinfo/libgdb/libgdb_toc.html#SEC4

specifies that a structure of function pointers should be used 
for

output.

struct gdb_output_vector
{
   /* output */
   void (*put_string) (struct gdb_output_vector *, char * str);
}


I couldn't quiet understand the need for such a complicated 
mechanism ,

more over I couldn't get the significance of both the input 
parametres.
actually i didn't get how does one implement the i/o mechanism in 
the

mentioned way.

can you please help me out with this......any help will be 
greatly

appreciated.

Thanking in advance


Nimesh Chanchani

             reply	other threads:[~2003-03-09 11:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-09 11:24 Nimesh D Chanchani [this message]
2003-03-25 22:28 ` Andrew Cagney

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=20030309112417.12639.qmail@webmail25.rediffmail.com \
    --to=nimeshc@rediffmail.com \
    --cc=gdb@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).