|
From: Nicholas N. <nj...@cs...> - 2005-08-26 21:20:02
|
On Fri, 26 Aug 2005, Tom Hughes wrote: > Hmm. It's not fully working for me... The problem is that gcc is > inserting calls to memcpy to handle structure assignments and those > are then unresolved when linking. Same here. If I put in a local version of memcpy() in m_libcbase.c next to VG_(memcpy)() those errors go away. Then I'm left with a weird error involving malloc() in VEX, even though you commented that out. I don't understand it at all. N ../coregrind/libcoregrind.a(.text+0x515e): In function `vgPlain_vprintf': /u/njn/grind/aspacem/coregrind/m_libcprint.c:95: undefined reference to `memcpy' ../coregrind/libcoregrind.a(.text+0xf4c4): In function `handle_SCSS_change': /u/njn/grind/aspacem/coregrind/m_signals.c:426: undefined reference to `memcpy' ../coregrind/libcoregrind.a(.text+0x10cf7): In function `queue_signal': /u/njn/grind/aspacem/coregrind/m_signals.c:1605: undefined reference to `memcpy' ../coregrind/libcoregrind.a(.text+0x197b5): In function `vgModuleLocal_read_callframe_info_dwarf2': /u/njn/grind/aspacem/coregrind/m_debuginfo/dwarf.c:2478: undefined reference to `memcpy' ../coregrind/libcoregrind.a(.text+0x316e5): In function `build_vg_sigframe': /u/njn/grind/aspacem/coregrind/m_sigframe/sigframe-x86-linux.c:447: undefined reference to `memcpy' ../coregrind/libcoregrind.a(.text+0x31702):/u/njn/grind/aspacem/coregrind/m_sigframe/sigframe-x86-linux.c:449: more undefined references to `memcpy' follow ../coregrind/libcoregrind.a(.text+0x5d662): In function `LibVEX_Alloc': /v/filer3/v1q009/njn/grind/aspacem/VEX/priv/main/vex_util.c:108: undefined reference to `malloc' |