A little unfortunate thing is that the test now requires elevated privileges, but that is true of all other DTrace tests as well, so I don't think that's a big deal.
BTW: there is Solaris specific ELF section for DTrace metadata and at first I wanted to fix the test by reading that one (with readelf -p .SUNW_dof <binary>). Unfortunately, the section includes more metadata than just available probes, and the now removed line probe is also present in the dumped strings (so test_check_probes passes, but test_missing_probes unexpectedly passes as well).
It's possible to use elfdump and do some binary parsing to extract only the available ones, but that is a huge overkill for a test like this. For those interested, the change is here: kulikjak@564e946
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Solaris does not use the notes section to list available probes (readelf -n <binary> returns nothing), which makes the test_check_probes fail.
This PR adds a Solaris specific path which gets all the available probes by listing those available in the running test process instead.
The output below is very different so the comparison needs to be updated a little as well.
>>> import subprocess >>> import os >>> res = subprocess.run(["dtrace", "-l", "-P", f"python{os.getpid()}"]) ID PROVIDER MODULE FUNCTION NAME 34 python1427 libpython3.16.so.1.0 sys_audit audit 35 python1427 libpython3.16.so.1.0 sys_audit_tstate.part.0 audit 36 python1427 libpython3.16.so.1.0 dtrace_function_entry function-entry 37 python1427 libpython3.16.so.1.0 _PyEval_EvalFrameDefault function-entry 38 python1427 libpython3.16.so.1.0 dtrace_function_return function-return 39 python1427 libpython3.16.so.1.0 _PyEval_EvalFrameDefault function-return 40 python1427 libpython3.16.so.1.0 gc_collect_main gc-done 41 python1427 libpython3.16.so.1.0 gc_collect_main gc-start 42 python1427 libpython3.16.so.1.0 import_find_and_load_with_name.isra.0 import-find-load-done 43 python1427 libpython3.16.so.1.0 import_find_and_load_with_name.isra.0 import-find-load-startA little unfortunate thing is that the test now requires elevated privileges, but that is true of all other DTrace tests as well, so I don't think that's a big deal.
BTW: there is Solaris specific ELF section for DTrace metadata and at first I wanted to fix the test by reading that one (with readelf -p .SUNW_dof <binary>). Unfortunately, the section includes more metadata than just available probes, and the now removed line probe is also present in the dumped strings (so test_check_probes passes, but test_missing_probes unexpectedly passes as well).
It's possible to use elfdump and do some binary parsing to extract only the available ones, but that is a huge overkill for a test like this. For those interested, the change is here: kulikjak@564e946