Ben Frederickson

> Updated the PR to include a fix for an off-by-one introduced by https://github.com/benfred/py-spy/pull/635, trivially reproducible with the following: I believe this is fixed by https://github.com/benfred/py-spy/pull/751 - can you verify...

thanks for the PR! > I briefly tested this on a Nvidia GH200 Thats a pretty nice machine to be testing on =) >There are still some minor cleanups needed,...

@SimonHeim did you build with 'cargo build --release --features unwind' ? You can also get the binaries from the GitHub actions artifacts , which should have precompiled wheels with this...

We do have some limited ability to show memory of local variables - via the `py-spy dump --locals` flag - which might be useful to you.

GIL detection is platform dependant for py-spy when profiling python versions before 3.12 - and we don't officially support the s390x platform. This isn't something we'll be able to help...

What OS and cpu architecture are you using ? Also where are you installing python from?. We test out py-spy in CI against python v3.8.0 on [osx](https://github.com/benfred/py-spy/actions/runs/16806624160/job/47600951530) and [windows](https://github.com/benfred/py-spy/actions/runs/16806624160/job/47600951584) ....

Can you explain a little more about your use-case? I understand that the `_config_version` field has been removed (and is only present here since the bindings were generated on v3.8.0b4...

/ok to test 760b3d1

/ok to test e6feca5