This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author twleung
Recipients belopolsky, bretthoerner, laca, movement, rhettinger, robert.kern, ronaldoussoren, skip.montanaro, twleung
Date 2009-01-28.03:06:37
SpamBayes Score 1.2188694e-11
Marked as misclassified No
Message-id <>
In-reply-to <>
I didn't run auto(re)conf.  After I did that, all was well.  However,  
the ustack provider doesn't appear to be working correctly.   I tried  
running the py_profile.d from the DTrace toolkit, and it doesn't show  
any stack traces, and when the script starts up it says

cc1: warning: /dev/fd/5 is shorter than expected

The basic function entry/exit probes appear to be working.

John +nosy'ed himself, so perhaps he'll have some insight?

On Jan 27, 2009, at 3:39 PM, Skip Montanaro wrote:

> Skip Montanaro <> added the comment:
> Ted> I tried building this on my Mac and got this;
> Forgive me if I'm preaching to the choir here.
> Did you run autoconf or autoreconf after applying the patch?  If not,
> @DTRACEOBJS@ would not be a substitutable string.  It's fairly  
> common (at
> least in the Python community) to omit modified configure scripts  
> from these
> sorts of patches because the changes to generated configure scripts  
> between
> different versions of autoconf are so massive that they dwarf the  
> actual
> functional changes in the patch, often by a couple orders of  
> magnitude.
> Skip
> _______________________________________
> Python tracker <>
> <>
> _______________________________________
Date User Action Args
2009-01-28 03:06:41twleungsetrecipients: + twleung, skip.montanaro, rhettinger, ronaldoussoren, belopolsky, movement, bretthoerner, laca, robert.kern
2009-01-28 03:06:38twleunglinkissue4111 messages
2009-01-28 03:06:37twleungcreate