This is the mail archive of the
archer@sourceware.org
mailing list for the Archer project.
Re: find-debuginfo.sh change for gdb index
- From: Tom Tromey <tromey at redhat dot com>
- To: Roland McGrath <roland at redhat dot com>
- Cc: Panu Matilainen <pmatilai at redhat dot com>, Project Archer <archer at sourceware dot org>
- Date: Tue, 06 Jul 2010 13:41:41 -0600
- Subject: Re: find-debuginfo.sh change for gdb index
- References: <m3vd91tqpl.fsf@fleche.redhat.com><20100629232147.C019548255@magilla.sf.frob.com><m3r5joscvs.fsf@fleche.redhat.com><20100630181436.518364C33C@magilla.sf.frob.com><m31vbos7lc.fsf@fleche.redhat.com> <m3y6dws151.fsf@fleche.redhat.com><20100630204424.3DCE34C33C@magilla.sf.frob.com><m3lj9wrz60.fsf@fleche.redhat.com><20100630221406.254AC4C33E@magilla.sf.frob.com><m339w1lkuu.fsf@fleche.redhat.com><alpine.LFD.2.00.1007051223290.8757@localhost><m38w5ocvcj.fsf@fleche.redhat.com><20100706191407.535874824F@magilla.sf.frob.com>
Roland> Doing this adds another interlocking requirement. The eu-strip
Roland> (libebl) code for -g matches the individual DWARF sections by
Roland> name. (Without -g, it strips all non-allocated sections, but
Roland> for -g it only strips the sections with recognized names.) So
Roland> that requires a (one-line) change in elfutils for the new
Roland> section name, and we'll need the new elfutils release in
Roland> buildroots before the new index-adding procedure goes in. (It
Roland> shouldn't be any problem to push this out quickly, but it needs
Roland> to go on your checklist so we coordinate it.)
I was thinking we would just objcopy the data into the .debug file in
find-debuginfo.sh.
Is there an advantage to doing it before the stripping?
Tom