lywsvip/reactos
1
0
Fork 0
mirror of https://github.com/reactos/reactos.git synced 2026-07-04 10:14:37 +08:00
Code Issues Packages Projects Releases Wiki Activity

DWARF debugging information confuses rsym, and DWARF-2 information from internal libraries (like libgcc) results in huge executables that don't even run on Windows. Therefore, before the rsym phase, strip all DWARF-2 sections

Browse Source 
This is a HACK for gcc builds compiled with DWARF-2 symbols (e.g. 4.3.2-tdm-1). The real solution (to be implemented soon) is to parse DWARF-2 line numbers in rsym

svn path=/trunk/; revision=37851
This commit is contained in:
KJK::Hyperion
2008-12-04 16:09:26 +00:00
parent bf1d153d93
commit 0e80776aff
1 changed files with 3 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
reactos/tools/rbuild/backend/mingw/modulehandler.cpp
View File

@@ -1428,6 +1428,9 @@ MingwModuleHandler::GenerateRunRsymCode () const
"ifneq ($(ROS_GENERATE_RSYM),no)\n" );
fprintf ( fMakefile,
"\t$(ECHO_RSYM)\n" );
// FIXME! workaround until rsym can extract line numbers from DWARF
fprintf ( fMakefile,
"\t$(Q)${strip} -R .debug_abbrev -R .debug_aranges -R .debug_frame -R .debug_info -R .debug_line -R .debug_pubnames -R .debug_macinfo -R .debug_str -R .debug_loc -R .debug_pubtypes -R .debug_ranges -R .debug_static_func -R .debug_static_vars -R .debug_types -R .debug_weaknames $@\n\n" );
fprintf ( fMakefile,
"\t$(Q)$(RSYM_TARGET) $@ $@\n\n" );
fprintf ( fMakefile,