[issue14776] Add SystemTap static markers

Changes by Łukasz Langa : -- resolution: -> out of date status: open -> closed superseder: -> Systemtap and DTrace support versions: +Python 3.6 -Python 3.5 ___ Python tracker

[issue14776] Add SystemTap static markers

Changes by cburroughs : -- nosy: +cburroughs ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pytho

[issue14776] Add SystemTap static markers

Changes by Nikhil Benesch : -- nosy: +benesch ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyth

[issue14776] Add SystemTap static markers

Changes by Xavier Morel : -- nosy: +xmorel ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.

[issue14776] Add SystemTap static markers

Bohuslav "Slavek" Kabrda added the comment: I opened a bug for tracking progress of development of the combined dtrace and systemtap support: http://bugs.python.org/issue21590 -- ___ Python tracker ___

[issue14776] Add SystemTap static markers

Jesús Cea Avión added the comment: Could you possibly create a new issue and add me to its NOSY? -- ___ Python tracker ___ ___ Python-

[issue14776] Add SystemTap static markers

Bohuslav "Slavek" Kabrda added the comment: @jcea: So here is my proposal for dealing with this: let's take what I currently have (e.g. tracepoints for function entry/function exit) and extend my patch to also work with DTrace in a similar fashion. Then, when we have a working patch for both S

[issue14776] Add SystemTap static markers

Jesús Cea Avión added the comment: I would. Just to point out that some dtrace weirdness like the stack walker is needed because dtrace probes are executed inside the OS kernel :-). Can we analyze case by case?. -- ___ Python tracker

[issue14776] Add SystemTap static markers

Bohuslav "Slavek" Kabrda added the comment: I'd be fine with adapting the patch to support both systemtap and dtrace, however I have very little knowledge of dtrace and I don't have a machine to test it on. @jcea would you be willing to work on such patch with me? I'm sure we could work on thi

[issue14776] Add SystemTap static markers

Martin v. Löwis added the comment: I still wish there was a patch that combined both dtrace and systemtap support, und used as much code sharing between them as feasible. I'd be +1 on such a patch, and -0 on two separate patches that achieve the same functionality, but on different code paths.

[issue14776] Add SystemTap static markers

Jesús Cea Avión added the comment: I would like to point out that if this patch gets accepted, maybe issue #13405 (updated, I keep an up to date version in my mercurial repo) should too. -- ___ Python tracker

[issue14776] Add SystemTap static markers

Changes by Terry J. Reedy : -- versions: +Python 3.5 -Python 3.4 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue14776] Add SystemTap static markers

Bohuslav "Slavek" Kabrda added the comment: As usual, I forgot to hg add the new files before running hg diff, so the newly created files didn't get added to the patch. Attaching a fixed version that hopefully has everything. AFAICS all the scripts that Fedora has are 1:1 copy of documentation

[issue14776] Add SystemTap static markers

Dave Malcolm added the comment: On Mon, 2014-05-19 at 14:15 +, Dave Malcolm wrote: > Dave Malcolm added the comment: > > On Mon, 2014-05-19 at 11:10 +, Bohuslav "Slavek" Kabrda wrote: > > Bohuslav "Slavek" Kabrda added the comment: > > > > Hi, > > I'd like to take this over after Dave M

[issue14776] Add SystemTap static markers

Dave Malcolm added the comment: On Mon, 2014-05-19 at 11:10 +, Bohuslav "Slavek" Kabrda wrote: > Bohuslav "Slavek" Kabrda added the comment: > > Hi, > I'd like to take this over after Dave Malcolm. I don't see any issues that > haven't been resolved, so my question is: What else can I do to

[issue14776] Add SystemTap static markers

Bohuslav "Slavek" Kabrda added the comment: Hi, I'd like to take this over after Dave Malcolm. I don't see any issues that haven't been resolved, so my question is: What else can I do to make this patch acceptable? I'm attaching a rebased version of this patch that applies to current default b

[issue14776] Add SystemTap static markers

Changes by Christian Heimes : -- nosy: +christian.heimes versions: +Python 3.4 -Python 3.3 ___ Python tracker ___ ___ Python-bugs-list

[issue14776] Add SystemTap static markers

Antoine Pitrou added the comment: Note that feature freeze happens after the first /beta/, so the alpha release isn't a showstopper. -- ___ Python tracker ___ __

[issue14776] Add SystemTap static markers

Robert Buchholz added the comment: It's been a year and the 3.4 alpha is approaching. What's the status of upstream inclusion of this patch? -- ___ Python tracker ___ __

[issue14776] Add SystemTap static markers

Changes by Robert Buchholz : -- nosy: +Robert.Buchholz ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://m

[issue14776] Add SystemTap static markers

Dave Malcolm added the comment: I'm attaching an updated version of the patch; I hope there's still time before Saturday to get it into 3.3 I found a bug in the configure script in the old patch: /usr/bin/dtrace was required, even without requesting systemtap. I've fixed it by adding a new

[issue14776] Add SystemTap static markers

Éric Araujo added the comment: > We currently have several locations for documentation: Don’t forget the wiki . It is much less curated than the other docs. > Though I don't want to block this feature on writing up a full guide to > debugging I started work on a debugging howto: #12913. Mayb

[issue14776] Add SystemTap static markers

Antoine Pitrou added the comment: I think it could go into "python setup and usage" (http://docs.python.org/dev/using/index.html), but that seems target at first-time users; or perhaps a HOWTO (http://docs.python.org/dev/howto/index.html), but it might make it less visible. Or a "debug and i

[issue14776] Add SystemTap static markers

Dave Malcolm added the comment: Thanks. I too am wondering where the documentation should go. We currently have several locations for documentation: (1) the man page (2) the "Doc" subdirectory aka docs.python.org (3) various text files in the source tree, such as Misc/SpecialBuilds.txt

[issue14776] Add SystemTap static markers

Changes by Dave Malcolm : Removed file: http://bugs.python.org/file25615/cpython-systemtap-2012-05-16-001.patch ___ Python tracker ___ ___ Py

[issue14776] Add SystemTap static markers

Changes by Dave Malcolm : -- Removed message: http://bugs.python.org/msg160914 ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue14776] Add SystemTap static markers

Changes by Dave Malcolm : -- Removed message: http://bugs.python.org/msg160913 ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue14776] Add SystemTap static markers

Dave Malcolm added the comment: (Sorry about msg160913; looks like my initial email response took about an hour to get through, and I'd subsequently commented using the webui form) -- ___ Python tracker _

[issue14776] Add SystemTap static markers

Dave Malcolm added the comment: On Wed, 2012-05-16 at 16:41 +, Antoine Pitrou wrote: > Antoine Pitrou added the comment: > > I tried the patch under Mageia 1 and got the following failure: > > test_systemtap skipped -- Test systemtap script did not run; stderr was: > b"Pass 1: parsed use

[issue14776] Add SystemTap static markers

Antoine Pitrou added the comment: > 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. Fair enough. I think the main patch looks go to go. It's clean and doesn't obscure core parts of the in

[issue14776] Add SystemTap static markers

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 systemta

[issue14776] Add SystemTap static markers

Antoine Pitrou added the comment: Still fails. So I tried the script by hand and got: $ stap - -vv -c true --vp 1 Created temporary directory "/tmp/stapBvo9zS" SystemTap translator/driver (version 1.3/0.152 non-git sources) Copyright (C) 2005-2010 Red Hat, Inc. and others This is free soft

[issue14776] Add SystemTap static markers

Dave Malcolm added the comment: > I tried the patch under Mageia 1 and got the following failure: Thanks. I'm attaching an updated patch which reworks test_systemtap so that (a) it turns up the verbosity of stap invocations from "-v" to "-vv" (b) it tests the "hello world" stap script on a

[issue14776] Add SystemTap static markers

Antoine Pitrou added the comment: I tried the patch under Mageia 1 and got the following failure: test_systemtap skipped -- Test systemtap script did not run; stderr was: b"Pass 1: parsed user script and 72 library script(s) using 56252virt/20964res/1828shr kb, in 70usr/0sys/82real ms.\nPass

[issue14776] Add SystemTap static markers

Changes by Dave Malcolm : -- nosy: +fche, scox ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue14776] Add SystemTap static markers

Changes by Bohuslav "Slavek" Kabrda : -- nosy: +bkabrda ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://

[issue14776] Add SystemTap static markers

Changes by Dave Malcolm : Added file: http://bugs.python.org/file25540/devguide-systemtap-2012-05-11-001.patch ___ Python tracker ___ ___ Pyt

[issue14776] Add SystemTap static markers

Dave Malcolm added the comment: Thanks Eric, Antoine and Mark. I'm attaching two new patches: a replacement patch for cpython, and a new patch for the devguide I've moved the docs to the dev guide, starting a new "Debugging and Instrumentation" section there. Changes to the cpython patch:

[issue14776] Add SystemTap static markers

Mark Wielaard added the comment: Just a comment that newer [eu]-readelf -n will provide a nicer view of the sdt ELF notes. You might want to suggest that in the documentation. e.g. $ eu-readelf -n /usr/lib64/libpython2.7.so Note section [ 1] '.note.gnu.build-id' of 36 bytes at offset 0x190:

[issue14776] Add SystemTap static markers

Changes by Mark Wielaard : -- nosy: +mjw ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org

[issue14776] Add SystemTap static markers

Antoine Pitrou added the comment: Well, at least it looks much cleaner that the dtrace patch. Two comments still: - is pysystemtap.h meant to be a public header? otherwise it should perhaps not end up in Include (I'm not sure what our policy is here) - perhaps get_frame_marker_info() and frien

[issue14776] Add SystemTap static markers

Éric Araujo added the comment: BTW if you don’t get feedback in a week or two you could go to python-dev; if there is no controversy nor implications on third-party code this will likely not require a PEP, only agreement between the core devs. Good luck! -- _

[issue14776] Add SystemTap static markers

Éric Araujo added the comment: I think the doc may be more at home in the Developer’s Guide (like the doc about GDB) rather that the new-user-oriented “Setup and Usage” doc. -- nosy: +eric.araujo ___ Python tracker

[issue14776] Add SystemTap static markers

New submission from Dave Malcolm : I'm attaching a patch which adds static markers for SystemTap for two probeable events within CPython's bytecode interpreter, along with test cases and documentation. I'm hoping to get this merged for 3.3; is this PEP-worthy, or can this be done through patc