[issue33424] 4.4. break and continue Statements, and else Clauses on Loops

[CH]

New submission from CH :

range function second parameter is excluded. Hence for x in range(2, n): will 
not execute when n = 2, and "2 is a prime number" will never appear.
Moreover, might need a break in the else block too.

--
messages: 316158
nosy: joesatriani
priority: normal
severity: normal
status: open
title: 4.4. break and continue Statements, and else Clauses on Loops

___
Python tracker 
<https://bugs.python.org/issue33424>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4111] Add Systemtap/DTrace probes

[Frank Ch. Eigler]

Frank Ch. Eigler  added the comment:

I believe the problem jcea is experiencing is with the
solaris (/linux?) branch of the configure.in:

if dtrace -G -o /dev/null -s $srcdir/Include/pydtrace.d 2>/dev/null

It seems solaris doesn't like the -o /dev/null part.  Try
specifying some real temporary file name instead.

--
nosy: +fche

___
Python tracker 
<http://bugs.python.org/issue4111>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue32599] Add dtrace hook for PyCFunction_Call

[Frank Ch. Eigler]

New submission from Frank Ch. Eigler :

Similar to https://bugs.python.org/issue31574, it would be useful the the 
interpreter allowed a tracing tool to hook the PyCFunction_Call() site, maybe 
via the C_TRACE() macro, kind of how it already does in  
_PyEval_EvalFrameDefault().  This would help diagnose problems in the C upcalls.

--
components: Interpreter Core
messages: 310278
nosy: fche
priority: normal
severity: normal
status: open
title: Add dtrace hook for PyCFunction_Call
type: performance

___
Python tracker 
<https://bugs.python.org/issue32599>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue13405] Add DTrace probes

[Frank Ch. Eigler]

Frank Ch. Eigler  added the comment:

> Stan, anybody working in SystemTap support, could you possibly
> create a new issue in the tracker to track specifically stap
> support?. You can depend on this bug, and coordinate effort. Clone
> my repository and use it as base.

I believe the only remotely-systemtap-specific stuff we suggested
would be useful would be the addition of that PyEval_GetFrame() value
as an extra argument for function entry/exit sdt.h calls.

I believe your patch already apprx. works against systemtap (and in
fact many dtrace idiosyncracies like asm("nop") are unnecessary here),
except for the inclusion of the /usr/bin/dtrace -G-generated header
file, as mentioned in <http://bugs.python.org/issue13405#msg149054>.

Do you think it is necessary to track that in a separate bug?

- FChE

--

___
Python tracker 
<http://bugs.python.org/issue13405>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue14776] Add SystemTap static markers

[Frank Ch. Eigler]

Frank Ch. Eigler  added the comment:

Hi -

On Wed, May 16, 2012 at 06:29:09PM +, Antoine Pitrou wrote:
> [...]
> No obvious error message. Who the hell designs such UIs? This seems
> as stupidly unfriendly as dtrace...

Sorry about that.  You're running a near-two-year-old version of
systemtap (1.3); error messages (and of course much functionality) has
improved since.

- FChE

--

___
Python tracker 
<http://bugs.python.org/issue14776>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com