gh-103650: Fix perf maps address format

[art049]

• Issue: perf maps address format #103650

[bedevere-bot]

Most changes to Python require a NEWS entry.

Please add it using the blurb_it web app or the blurb command-line tool.

[ghost]

All commit authors signed the Contributor License Agreement.

[bedevere-bot]

Most changes to Python require a NEWS entry.

Please add it using the blurb_it web app or the blurb command-line tool.

[terryjreedy]

I think that this should wait until Pablo verifies that it is indeed the implementation that should be changed.

[carljm]

@art049 did you verify that the new output after this PR works the same with perf?

@terryjreedy since the relevant docs here are the external perf map specification, not the CPython docs, it seems clear that the implementation in CPython should match the specification. There is no option to change the specification, we don't own it.

[art049]

@art049 did you verify that the new output after this PR works the same with perf?

Yes, also there are existing tests checking this:

cpython/Lib/test/test_perf_profiler.py

Lines 304 to 327 in 0ba49e2

	deftest_python_calls_appear_in_the_stack_if_perf_activated(self):
	withtemp_dir() asscript_dir:
	code="""if 1:
	def foo(n):
	x = 0
	for i in range(n):
	x += i
	def bar(n):
	foo(n)
	def baz(n):
	bar(n)
	baz(10000000)
	"""
	script=make_script(script_dir, "perftest", code)
	stdout, stderr=run_perf(script_dir, sys.executable, "-Xperf", script)
	self.assertEqual(stderr, "")
	self.assertIn(f"py::foo:{script}", stdout)
	self.assertIn(f"py::bar:{script}", stdout)
	self.assertIn(f"py::baz:{script}", stdout)

[bedevere-bot]

🤖 New build scheduled with the buildbot fleet by @pablogsal for commit 0ba49e2 🤖

If you want to schedule another build, you need to add the 🔨 test-with-buildbots label again.

[pablogsal]

Running this PR with the buildbots as the perf stuff is not checked on regular CI.