Jose Luis Alarcon Sanchez, le mar. 10 févr. 2026 20:41:38 +0100, a ecrit: > El Tue, 10 Feb 2026 19:23:17 +0100 > Samuel Thibault <[email protected]> escribió: > > Hello, > > > > Jose Luis Alarcon Sanchez, le mar. 10 févr. 2026 15:37:08 +0100, a > > ecrit: > > > How is it possible that at the end of last year, from one > > > day to the next, the two best web browsers available on GNU/Hurd, > > > Luakit and Surf, which are very similar and based on the same > > > scripting language, Lua, went from working very satisfactorily to > > > instantly terminating when launched, with the brief output ‘abort’? > > > > > > > Because of a bug? The abort message would probably be very > > informative. Or a gdb backtrace, etc. > > > > > Is it possible to investigate why this happened?. > > > > Sure. For a simple start, you can check what package got upgraded > > in between, and then try to downgrade/upgrade to verify which exact > > package pose problems. But also simply actually pasting the abortion > > message would provide the list with *way* more information than just > > "terminates". > > I don't know how to get a "register" of the upgrades realized at that > time (it was last week of 2025, i'm sure of it).
It's all in /var/log/dpkg.log > In the attached screenshot it's collected the proccess of typing 'surf' > and 'luakit' in the command line. If i can help in this investigation > in any way, let my know, cos i'm eager to help. Ok, it's indeed not informative. But then run it inside gdb and type "run" then "bt", having installed the -dbgsym packages as needed to get the source code lines, and the abortion backtrace will be informative. Samuel
