This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: extending Gdb to display app specific data

To: bstell at netscape dot com
Subject: Re: extending Gdb to display app specific data
From: Eli Zaretskii <eliz at delorie dot com>
Date: Sat, 11 Nov 2000 02:33:31 -0500 (EST)
CC: gdb at sources dot redhat dot com
References: <3A0B4885.B2384AE7@netscape.com> <200011101039.FAA29785@indy.delorie.com> <3A0C2791.A33BE9AC@ix.netcom.com> <200011102009.PAA00126@indy.delorie.com> <3A0C8E19.A8A6D355@netscape.com> <20001110191444.26019@cse.cygnus.com> <3A0C935B.AE3C0AF9@netscape.com>
Reply-to: Eli Zaretskii <eliz at is dot elta dot co dot il>

> Date: Fri, 10 Nov 2000 16:31:23 -0800
> From: bstell@netscape.com (Brian Stell)
> 
> So how do we do this without requiring the end
> user to know the exact data type of a variable
> in any routine they pass thru and without requiring
> the end user memorize the routine names?

The function (from the debugged program) that is used to print the
data type could find out the type itself.  That's what `debug_print'
in Emacs does, albeit indirectly.

References:
- extending Gdb to display app specific data
  - From: Brian Stell
- Re: extending Gdb to display app specific data
  - From: Eli Zaretskii
- Re: extending Gdb to display app specific data
  - From: bstell
- Re: extending Gdb to display app specific data
  - From: Eli Zaretskii
- Re: extending Gdb to display app specific data
  - From: Brian Stell
- Re: extending Gdb to display app specific data
  - From: Michael Meissner
- Re: extending Gdb to display app specific data
  - From: Brian Stell

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]