This is the mail archive of the egcs@egcs.cygnus.com mailing list for the EGCS project. See the EGCS home page for more information.
> From: dmartin@clifton-labs.com (Dale E. Martin) > Date: 08 Mar 1999 15:32:06 -0500 > Jason Merrill <jason@cygnus.com> writes: > > A testcase so we can reproduce the problem. > I'd love to be able to provide a small testcase. The system I'm working > with is large though. The small cases I've played with work fine. > I guess my main problem is that I'm well versed in solving linker > problems using "nm" and experience, but I don't have any idea about > how to debug ".rpo" files and all of that. Is there documentation > available describing what's going on besides the egcs info file? I can try and help you submit a bug report... First identify what symbol isn't being generated. Be sure to figure out the undemangled version. confirm with nm. Then, find out what file uses it (nm | grep 'U sym' will confirm a use), and that it could be instantiated in. Review output from -E on the compile and ensure that the thing you want a definition for is _defined_. If not _defined_, fix source code or go back to this step. grep around in the rpo file for the symbol, and file this information along with the souce code to this _one_ file along with the linker error message about not finding it. Include the undemangled version of the error message, please, not the demangled version. Ensure that the spelling is byte for byte identical. This is mostly the same process of non-template code. If you can reduce the size of the file, without affecting the fundamentals of it, that helps, and realistically will increase the odds of the bug being fixed, but it isn't necessary for submission of a bug report. Only compression is required if it is large. Hope this helps.