On Thu, Oct 21, 2004 at 01:30:53AM +0300, Maxim Sobolev wrote: > Maxim Sobolev wrote: > > >OK, I've just checked objcopy manpage and found that there is actually a > >better way which combines best properties of both approach. In modern > >GNU toolchain it is possible to split executable and debugging info into > >two separate files, but put a reference into executable, so that you > >don't have to worry about how to load debugging symbols: > > [...] > >I checked, this works like a charm with our current toolchain/gdb. This > >allows us to do the following clever trick WRT kernel debug: > > > >1. Compile kernel/modules with debugging symbols; > >2. Split out executable and debugging pieces for each module; > >3. Associate each executable file with appropriate debug file; > >4. Install executable into /boot/kernel as usually; > >5. Install real debugging into /var/something, put symlink to it into > >/boot/kernel. > > > >By the way, this approach can be extended to be an option of buildworld > >as well! It can be good way to trade developers' time for some hdd > >space, since with this option "on" you will always be able to debug > >misbehaving application/library without the need to recompile/reinstall > >everything! > > BTW, it also allows us to do create separate "debug" distribution for > release CDs. So that one can do binary install and then add debugging > symbols if necessary. > Now go and hack kmod.mk and kern.post.mk, and I will go to bed. ;) Psycho! :-) Cheers, -- Ruslan Ermilov ru_at_FreeBSD.org FreeBSD committer
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:18 UTC