This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Hi Yookyung, > It looks to me that only ".debug_line" section of > dwarf2 has been implemented. No, other dwarf2 debug sections can also be generated. > I am sure that from-assembly-to-object level that section > might be most important but I am just wondering whether the section > such as ".debug_info" has been implemented also. Have a look at the code in gas/dwarf2dbg.c. In particular the function dwarf2_finish() which calls out_debug_info(). Note - this file has been modified since the 2.10.1 release, so you may want to obtain the latest version from the CVS repository, or wait for the 2.11 sources to be released. > Yet another question is about ".mdebug". > Actually I do not know anything about MDEBUG format. > At first hand, I thought that "stabs" information is somehow > in ".mdebug" section, because the assembly code generated > seemed to have stabs information. > However, having read your reply, I am wondering whether > it is a debug format different from stabs. Yes it is different. As I understand it, it also quite hard to obtain printed/on-line documentation for the format, but if you examine the source code in gcc/mips-tfile.c, there should be enough there to help you. Cheers Nick ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |