This is the mail archive of the gdb@sourceware.org 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]
Other format: [Raw text]

Re: asynchronous MI output commands


On Sun, May 07, 2006 at 09:26:15PM -0400, Daniel Jacobowitz wrote:
> On Sun, May 07, 2006 at 08:29:35PM -0400, Bob Rossi wrote:
> > OK. I start with the MI output. I use bison to convert that into an
> > abstract parse tree. Now, I am working on a solution to take the
> > abstract parse tree and turn it into a simple to use representation for
> > the front end (ADT). I gave the example earlier, taking the abstract parse
> > tree for -file-list-exec-source-file 
> >   ^done,line="26",file="test.c",fullname="/home/bob/cvs/cgdb/cgdb.mi/builddir/test.c"
> > and turn that into
> >   struct file_list_exec_source_file
> >   {
> >     int line;
> >     char *file;
> >     char *fullname;
> >   };
> >   struct file_list_exec_source_file result = { 26, "test.c", "/home..."};
> 
> [What's ADT mean then?  The "A" can't be abstract, there's nothing
> abstract about this.]

Oops, my terminology is off again. I'm sorry. I'll try to do better in
the future. I simply want to create a specific struct for each MI output
command. 

I'm making some progress on this task. I'm going to post what I've got
in a few days. I'm not happy with the way it's turning out, due to the
fact that the MI output commands don't describe what kind of output
command they are. However, with comments from you and Nick, I'm sure I
can work it out.

Thanks,
Bob Rossi


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