Mail Archives: djgpp-workers/2000/04/06/06:02:30
On 3 Apr 2000, at 10:57, Eli Zaretskii wrote:
>
> On Mon, 3 Apr 2000, Andris Pavenis wrote:
>
> > > > Also. Had to hack RHIDE rather much to be able to build it using this
> > > > snapshot.
> > >
> > > Could you summarize the problems you had with building RHIDE? Is
> > > there something in GDB 5.0 that should be changed to make it easier?
> >
> > I don't think so. RHIDE should be modified in this case.
>
Earlier RHIDE provided it's own copy of fputc_unfiltered() (which is
ugly hack of course). Now I changed it to use mem_fileopen() for both
gdb_stdout and gdb_stderr.
One nuisance:
to get actual positon in ui_file opened with mem_fileopen currently
only possibility is to retrieve entire buffer with ui_file_xstrdup()
(RHIDE needs to get such position currently). I think it would be nice
to add something like
ui_file_xstrlen()
to get length of buffer only (really it's current pointer) like (untested):
long ui_file_xstrlen (struct ui_file *file)
{
if (file->magic==&mem_file_magic)
{
struct mem_file * mem = file->to_data;
if (mem->magic==&mem_file_magic)
return mem->length_buffer;
}
return 0;
}
> Perhaps in the long run RHIDE should switch to the GDB-mi interface
> instead of the annotations. It seems like the GDB developers want to
> deprecate annotations, they are kept mainly because Emacs uses that
> interface.
>
> Note that currently, the DJGPP version of GDB is built without GDB-mi. I
> need time (which I don't have ;-) to work on adding that.
Andris
- Raw text -