This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: Repost: Inaccurate function parameter location in debug info with gcc 3.x and 4.0
- From: fche at redhat dot com (Frank Ch. Eigler)
- To: "Yi Feng" <ericyifeng at gmail dot com>
- Cc: systemtap at sources dot redhat dot com
- Date: 15 May 2006 22:15:44 -0400
- Subject: Re: Repost: Inaccurate function parameter location in debug info with gcc 3.x and 4.0
- References: <4acfb6400605151055x7b4585b8r68f0c6a835668fa9@mail.gmail.com>
"Yi Feng" <ericyifeng@gmail.com> writes:
> [...] I have encountered a problem with the DWARF debug info when
> compiling the kernel with gcc 3.x and 4.0 with optimization flags of
> either -O1 or -O2. When looking at the parameter locations of, for
> example, sys_read, the debug info says they are all in EAX [...]
Something must be very odd about your build or systemtap script, since
in general parameter access is working all right. We even have a
sys_open-related test in the pass-5 test suite, and it succeeds on a
variety of kernel and compiler versions.
If you can share more details about what you're seeing (relevant
chunks of dwarf readelf data, script, "stap -vvvv" type output) ... we
may be able to help.
- FChE