This is the mail archive of the
gdb@sourceware.cygnus.com
mailing list for the GDB project.
Re: mdebug
- To: davea at dsl-quasar dot corp dot sgi dot com (David B. Anderson)
- Subject: Re: mdebug
- From: Elena Zannoni <ezannoni at cygnus dot com>
- Date: Fri, 31 Mar 2000 18:12:43 -0500 (EST)
- Cc: gdb at sourceware dot cygnus dot com
- References: <200003312258.OAA25181@dsl-quasar.corp.sgi.com>
Thanks David, I did find your paper.
And yes, I have a specific question. Does mdebug let the user specify
a procedure like 'main()' in a section other than .text?
Thanks
Elena
David B. Anderson writes:
>
>
>
> Elena Zannoni <ezannoni@cygnus.com> writes:
> >Does anybody know something about mdebug?
>
> Yes.
>
> >I am trying to figure out a problem in gdb which untilmately is due
> >to some limitation of mdebug.
> >Is there any documentation at all about how the debug symbols are built?
>
> http://reality.sgi.com/davea/objectinfo.html
> Look early in the page for:
>
> one part of the old 32bit ABI for MIPS
> is the mdebug debugging information.
> A postscript file with the only currently
> available description of this data is here (119Kbytes)
>
> It is is an old paper I wrote on mdebug.
> Not too well written, but... what else is there?
> Perhaps it will help. Does not mention limits, though.
> The limits are implicit in various structs. Perhaps
> 'explicit' is a better word :-)
>
> If you have any questions let me know.
> (whether I'll know the answer is something else...)
>
> I don't know too much about DEC or other *extensions*
> to mdebug. Just sgi's. But there are certainly some
> important limitations in mdebug. Like 64K procedures (at most).
> SGI did some hack extensions, but ... never mind.
>
> davea@sgi.com