This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Target variable that was defined by our own kernel module

From: David Smith <dsmith at redhat dot com>
To: John Liang <jliang at ibrix dot com>
Cc: "'Systemtap List'" <systemtap at sources dot redhat dot com>
Date: Tue, 29 May 2007 13:19:02 -0500
Subject: Re: Target variable that was defined by our own kernel module
References: <46531C6E.3010502@redhat.com> <20070528182305.GD7882@Krystal> <465C298E.5040808@redhat.com> <000b01c7a1fb$bf426050$800101df@ibrixfaf958395> <465C4228.9030907@redhat.com> <000901c7a216$9f309550$800101df@ibrixfaf958395>

John Liang wrote:

David,

Do you mean I need to create a mymodule-debuginfo rpm in the same way as for kernel-debuginfo of Linux?

Yes or no - depending on how you compile your module.

If you are building via rpmbuild, it should automatically create a debuginfo rpm for you which you would then install.

If you are building by hand or via a Makefile, you'll need to ensure the module isn't stripped (I believe).

Also, a more exact error message could help us out here.

--
David Smith
dsmith@redhat.com
Red Hat
http://www.redhat.com
256.217.0141 (direct)
256.837.0057 (fax)

References:
- Linux kernel marker questions
  - From: David Smith
- Re: Linux kernel marker questions
  - From: Mathieu Desnoyers
- Re: Linux kernel marker questions
  - From: David Smith
- Target variable that was defined by our own kernel module
  - From: John Liang
- Re: Target variable that was defined by our own kernel module
  - From: David Smith
- RE: Target variable that was defined by our own kernel module
  - From: John Liang

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]