Michał Górny

Well, I'm guessing they really dislike something about my setup then… I guess it's either how I'm configuring/building LLVM or something about my hardware (FreeBSD is running on qemu with...

> I don't have a FreeBSD system at hand to test it quickly [...]. Well, it fails for me on Linux as well. If you could try building with the...

I'm afraid that's not it. It fails through the usual `check-lldb` for me consistently, and I'm sure I have an up-to-date `lldb-server`(after all, this is one of the things I'm...

It happens just the same on my Gentoo Linux system. ``` (lldb) target create "bin/lli" Current executable set to '/home/mgorny/git/llvm-project/build/bin/lli' (x86_64). (lldb) b jitbp Breakpoint 1: no locations (pending). WARNING:...

``` (lldb) target create "bin/lli" Current executable set to '/home/mgorny/git/llvm-project/build/bin/lli' (x86_64). (lldb) log enable lldb jit (lldb) run tools/lldb/test/Shell/Breakpoint/Output/jit-loader_jitlink_elf.test.tmp.ll lldb JITLoaderGDB::SetJITBreakpoint looking for JIT register hook lldb JITLoaderGDB::SetJITBreakpoint looking for...

> Alright, then LLDB doesn't find the GDB JIT Interface symbols `__jit_debug_register_code` and `__jit_debug_register_descriptor`. Make sure `lli` exposes them: > > ``` > $ llvm-nm bin/lli | grep __jit_debug >...

Curious enough, it seems to work fine when using dylib rather than split shared libraries, even though the symbol is in `.so` rather than the executable ``` $ nm -B...

I suppose I could give more context: I'm currently testing Python packages in Gentoo against Python 3.10. However, I am unable to test PySocks because its tests work only with...

If you mean beyond the GitHub issues — I don't know. However, he doesn't seem to have any recent public GitHub activity. That said, I think we're at the point...

Not at all, Gentoo stable is at 1.1.1o already.