This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: [Ksummit-2008-discuss] DTrace
- From: Sam Ravnborg <sam at ravnborg dot org>
- To: Theodore Tso <tytso at mit dot edu>
- Cc: Roland McGrath <roland at redhat dot com>, ksummit-2008-discuss at lists dot linux-foundation dot org, systemtap at sources dot redhat dot com
- Date: Tue, 1 Jul 2008 13:05:17 +0200
- Subject: Re: [Ksummit-2008-discuss] DTrace
- References: <20080630010423.GA7068@redhat.com> <20080630181959.GA7988@mit.edu> <20080630192533.GE21660@redhat.com> <20080630201031.GF7988@mit.edu> <20080630204219.GA6631@redhat.com> <20080701024140.GB28143@mit.edu> <20080701070746.C6DAD15420E@magilla.localdomain> <20080701101507.GB22717@mit.edu>
On Tue, Jul 01, 2008 at 06:15:07AM -0400, Theodore Tso wrote:
>
> I've pulled apart RHEL's rpm macro magic before, and it's not a
> pleasant wading through all of the files; maybe we can teach the
> native kernel build infrastructure how to create debuginfo files so
> that each distribution doesn't have to re-invent the wheel from
> scratch, but rather can reuse common infrastructure in Kbuild....
What is needed to create debuginfo files?
Seems like a simple thing to integrate in kbuild
if this is per file or per module.
If it is for the kernel as a whole things gets a bit more complex.
Sam