Lennart Poettering
Lennart Poettering
Please enable debug logging in resolved (`systemctl service-log-level systemd-resolved debug`), reproduce the issue, and provide the logs this generated (i.e. `journalctl -u systemd-resolved`)
hmm, weird. Any chance you can install debug symbols for this, and install gdb and then attach gdb to the running instance and set a breakpoint to `vl_method_resolve_hostname_complete` and then...
when i try to resolve the same hostname here, all works, so this is really strange
btw, if the debuginfod urls are embedded in the json data, we could could combine that with the build id, and the backtrace source files/line numbers and generate terinal clickable...
(but i guess we don't embed the debuginfo url in fedora yet, do we?
maybe we should embed a "format string" into the json data for reconstructing the package name? i.e. "%n-%a-%v" or so
But carrying this database of mappings sucks. We shouldn't have to do this in generic code.
at the very least, encapsulate this somewhere. i.e. a new helper `char *build_package_name(const char *type, const char *name, const char *arch, const char *version)`, but littering such distro specific hacks...
> I think that's unnecessary. It'd mean a few bytes wasted in every package, and a lot of complexity to parse the format string. The concatenation pattern is not magic,...
> No, we don't. And I'm not sure if we should. Debuginfod is great for usability, no doubt, but there are problems with trust and security. Generally gdb will fully...