| 17 Nov 2025 |
 K900 | libgallium-25.3.0.so@0x1a8f444 that is | 09:04:13 |
 Yureka (she/her) | how do I use addr2line with separate debug output? | 09:08:04 |
| K900 | It should just read the headers I think. | 09:09:13 |
| K900 | * It should just read the headers I think? | 09:09:19 |
 dramforever | In reply to @k900:0upti.me
@hexa we're pushing symbols for the entire closure right? libgallium isn't in the closure, it's in /run/opengl-driver | 09:11:04 |
| dramforever | uh | 09:11:16 |
| dramforever | not in the library closure | 09:11:23 |
| dramforever | if it's not in the nix closure i'd be very surprised | 09:11:33 |
| dramforever | but that's all i can think of | 09:11:50 |
| Yureka (she/her) | As in how do I invoke it? | 09:12:26 |
| dramforever | addr2line -e /path/to/libgallium.so 0x1a8fandsuch | 09:13:09 |
| Yureka (she/her) | [yuka@m1:~/proj/nixpkgs]$ addr2line 0x1a8f444 -e result/lib/libgallium-25.3.0.so
??:?
[yuka@m1:~/proj/nixpkgs]$
| 09:13:16 |
