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: Probe on function entry rather than the end of the prolog (s390x only)

From: fche at redhat dot com (Frank Ch. Eigler)
To: Roland McGrath <roland at redhat dot com>
Cc: David Wilder <dwilder at us dot ibm dot com>, systemtap at sources dot redhat dot com
Date: 01 Feb 2007 09:47:05 -0500
Subject: Re: Probe on function entry rather than the end of the prolog (s390x only)
References: <y0my7nid3fg.fsf@ton.toronto.redhat.com> <20070201035039.313F31800E9@magilla.sf.frob.com>

Roland McGrath <roland@redhat.com> writes:

> I don't think that flies so well.  The bugs we hit in older
> compilers were location lists that looked fine but were incorrect
> for the prologue regions.  There isn't any automatic way to identify
> those location lists as bad.

Too bad.  OK, then let's gather some data about compiler versions and
architectures.  If we find a reasonable and documentable dividing line
between working and not working, then we can make systemtap assume the
former.  (We could retain a discreet switch such as an environment
variable to activate the prologue code for people stuck with
non-working systems.)

- FChE

Follow-Ups:
- Re: Probe on function entry rather than the end of the prolog (s390x only)
  - From: David Wilder
- Re: Probe on function entry rather than the end of the prolog (s390x only)
  - From: Roland McGrath

References:
- Re: Probe on function entry rather than the end of the prolog (s390x only)
  - From: Frank Ch. Eigler
- Re: Probe on function entry rather than the end of the prolog (s390x only)
  - From: Roland McGrath

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