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: "Stone, Joshua I" <joshua dot i dot stone at intel dot com>
To: David Smith <dsmith at redhat dot com>
Cc: John Liang <jliang at ibrix dot com>, 'Systemtap List' <systemtap at sources dot redhat dot com>
Date: Tue, 29 May 2007 11:03:47 -0700
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>

David Smith wrote:

John Liang wrote:
[...]

It looks if $myparm is a data structure defined in Linux Kernel,
It would compile and run without problem; but if it is a defined
by my own module, then it gave me a "unresolved symbol error for
$myparm".
Any suggestions to solve this?

Make sure the debug information is installed for your kernel module.

If it were a problem of locating the debuginfo, I expect that it wouldn't even resolve the function, right?

It still may be a case of inadequate debugging information though. Perhaps that variable got optimized away, or it may be one of our beloved problems with gcc.

Josh

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

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