> > > > Let's see if I've managed to divine the use case that you're talking > about here so we can attempt to refocus the discussion somewhat: > > > > a) You ship headers and libraries to customers. > > b) You will not or, at least, have not shipped debug info to those > customers. > > c) For this case in particular: > > 1) The headers contain a polymorphic base class > > 2) Customers derive from this polymorphic base class > > 3) Linking still works since the customer has the library but not the > debug info for the base class where the key function was emitted. > > > > Is this correct? > > yes, this is what is got our kernel group filing bugs. >
So to confirm, you have a situation where you cannot rely on the fact that debug information exists for any object file past the current one so you need a way to turn off any assumption anywhere in debug info generation that something may or will be defined in another unit? -eric
_______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
