GDB reference manual

Hi all, 
	I've developed an IDE for C++ and I'm about to provide a
debugger for
it using GDB. But I could not find any reference manual
containing the
gdb_* functions (API) listings and explanations.

	I wonder how people could develop IDEs and GDB frontends
like anjuta,
Kgdb, xgdb and so on using GDB. I might be missing some
manuals. I'd
really appreciate it if someone could tell me where to find
the manuals.

Cheers,
Hossein Aminaiee

On Mon, May 28, 2007 at 03:42:31PM +0330, Hossein Aminaiee
wrote:
> Hi all, 
> 	I've developed an IDE for C++ and I'm about to provide
a debugger for
> it using GDB. But I could not find any reference manual
containing the
> gdb_* functions (API) listings and explanations.

That's because you shouldn't be using those.  Use GDB/MI,
which is
described in the manual.

-- 
Daniel Jacobowitz
CodeSourcery

Hi,

I have searched the whole GDB internal manual and I could
find
explanations on ui_* but gdb_* functions. Would you please
indicate the
exact page of which manual? Please send me the url of the
manual you are
using.

Cheers,
Hossein Aminaiee


On Mon, 2007-05-28 at 08:54 -0700, Daniel Jacobowitz wrote:
> On Mon, May 28, 2007 at 03:42:31PM +0330, Hossein
Aminaiee wrote:
> > Hi all, 
> > 	I've developed an IDE for C++ and I'm about to
provide a debugger for
> > it using GDB. But I could not find any reference
manual containing the
> > gdb_* functions (API) listings and explanations.
> 
> That's because you shouldn't be using those.  Use
GDB/MI, which is
> described in the manual.
> 

On 28/05/07, Hossein Aminaiee <aminaieegmail.com> wrote:
> Hi,
>
> I have searched the whole GDB internal manual and I
could find
> explanations on ui_* but gdb_* functions. Would you
please indicate the
> exact page of which manual? Please send me the url of
the manual you are
> using.

It can be found in the GDB user guide, not the internals
manual. It is
under chapter 24. Quoting from the start of this chapter:

"gdb/mi is a line based machine oriented text interface
to gdb and is
activated by specifying
using the '--interpreter' command line option (see Section
2.1.2 [Mode
Options], page 13).
It is specifically intended to support the development of
systems
which use the debugger as
just one small component of a larger system."

Hope that helps.

Rob Quill

>
> Cheers,
> Hossein Aminaiee
>
>
> On Mon, 2007-05-28 at 08:54 -0700, Daniel Jacobowitz
wrote:
> > On Mon, May 28, 2007 at 03:42:31PM +0330, Hossein
Aminaiee wrote:
> > > Hi all,
> > >     I've developed an IDE for C++ and I'm
about to provide a debugger for
> > > it using GDB. But I could not find any
reference manual containing the
> > > gdb_* functions (API) listings and
explanations.
> >
> > That's because you shouldn't be using those.  Use
GDB/MI, which is
> > described in the manual.
> >
>
>

Hi,
	I read the manual and I found the GDB/MI useful. I really
appreciate
your help. What I guessed from the manual that one should
start a gdb
process in the background and communicate with it using the
GDB/MI
commands. Am I wrong? But how to send MI commands to the
GDB? Should GDB
be started using the input/output redirection?
	
	Is there any tiny source examples of using GDB/MI?
Specially
demonstrating the communication with GDB from a programmers
point of
view?

	I explored a couple of frontends for GDB like rhide and I
figured out
that they've added the GDB/MI source files to their project
and compiled
them into their binaries. But what about the libgdb? Is it
possible to
use libgdb.so? 

Cheers,
Hossein Aminaiee


On Mon, 2007-05-28 at 15:07 +0100, Rob Quill wrote:
> On 28/05/07, Hossein Aminaiee <aminaieegmail.com> wrote:
> > Hi,
> >
> > I have searched the whole GDB internal manual and
I could find
> > explanations on ui_* but gdb_* functions. Would
you please indicate the
> > exact page of which manual? Please send me the url
of the manual you are
> > using.
> 
> It can be found in the GDB user guide, not the
internals manual. It is
> under chapter 24. Quoting from the start of this
chapter:
> 
> "gdb/mi is a line based machine oriented text
interface to gdb and is
> activated by specifying
> using the '--interpreter' command line option (see
Section 2.1.2 [Mode
> Options], page 13).
> It is specifically intended to support the development
of systems
> which use the debugger as
> just one small component of a larger system."
> 
> Hope that helps.
> 
> Rob Quill
> 
> >
> > Cheers,
> > Hossein Aminaiee
> >
> >
> > On Mon, 2007-05-28 at 08:54 -0700, Daniel
Jacobowitz wrote:
> > > On Mon, May 28, 2007 at 03:42:31PM +0330,
Hossein Aminaiee wrote:
> > > > Hi all,
> > > >     I've developed an IDE for C++ and
I'm about to provide a debugger for
> > > > it using GDB. But I could not find any
reference manual containing the
> > > > gdb_* functions (API) listings and
explanations.
> > >
> > > That's because you shouldn't be using those. 
Use GDB/MI, which is
> > > described in the manual.
> > >
> >
> >

Hi,
	I read the manual and I found the GDB/MI useful. I really
appreciate
your help. What I guessed from the manual that one should
start a gdb
process in the background and communicate with it using the
GDB/MI
commands. Am I wrong? But how to send MI commands to the
GDB? Should GDB
be started using the input/output redirection?
	
	Is there any tiny source examples of using GDB/MI?
Specially
demonstrating the communication with GDB from a programmers
point of
view?

	I explored a couple of frontends for GDB like rhide and I
figured out
that they've added the GDB/MI source files to their project
and compiled
them into their binaries. But what about the libgdb? Is it
possible to
use libgdb.so? 

Cheers,
Hossein Aminaiee


On Mon, 2007-05-28 at 15:07 +0100, Rob Quill wrote:
> On 28/05/07, Hossein Aminaiee <aminaieegmail.com> wrote:
> > Hi,
> >
> > I have searched the whole GDB internal manual and
I could find
> > explanations on ui_* but gdb_* functions. Would
you please indicate the
> > exact page of which manual? Please send me the url
of the manual you are
> > using.
> 
> It can be found in the GDB user guide, not the
internals manual. It is
> under chapter 24. Quoting from the start of this
chapter:
> 
> "gdb/mi is a line based machine oriented text
interface to gdb and is
> activated by specifying
> using the '--interpreter' command line option (see
Section 2.1.2 [Mode
> Options], page 13).
> It is specifically intended to support the development
of systems
> which use the debugger as
> just one small component of a larger system."
> 
> Hope that helps.
> 
> Rob Quill
> 
> >
> > Cheers,
> > Hossein Aminaiee
> >
> >
> > On Mon, 2007-05-28 at 08:54 -0700, Daniel
Jacobowitz wrote:
> > > On Mon, May 28, 2007 at 03:42:31PM +0330,
Hossein Aminaiee wrote:
> > > > Hi all,
> > > >     I've developed an IDE for C++ and
I'm about to provide a debugger for
> > > > it using GDB. But I could not find any
reference manual containing the
> > > > gdb_* functions (API) listings and
explanations.
> > >
> > > That's because you shouldn't be using those. 
Use GDB/MI, which is
> > > described in the manual.
> > >
> >
> >

On Wed, May 30, 2007 at 01:02:49PM +0330, Hossein Aminaiee
wrote:
> Hi,
> 	I read the manual and I found the GDB/MI useful. I
really appreciate
> your help. What I guessed from the manual that one
should start a gdb
> process in the background and communicate with it using
the GDB/MI
> commands. Am I wrong? But how to send MI commands to
the GDB? Should GDB
> be started using the input/output redirection?

Right.

> 	I explored a couple of frontends for GDB like rhide
and I figured out
> that they've added the GDB/MI source files to their
project and compiled
> them into their binaries. But what about the libgdb? Is
it possible to
> use libgdb.so? 

Not really.

-- 
Daniel Jacobowitz
CodeSourcery