Control: tag -1 patch pending Control: reassign -1 network-console Hi,
Frank Gard <frank.g...@exirius.de> (2019-05-02): > Am 02.05.19 um 09:43 schrieb Cyril Brulebois: > > Hi again, > > > > […] > > OK, thanks. That confirms at least the echo instruction I quoted is > > executed, but gen-crypt didn't do its job… > > […] > > … which is understandable given the segfault. > > […] > > > > Please mention at the very least your architecture and the target > > device, in case the segfault is hardware/architecture-dependent. This > > could be some trivial bug, but let's see what you're running d-i on. > > Please find attached the complete output of dmesg. I hope there's all > information you need. If not, please let me know. That was enough, thanks. I tend to think about arm* devices whenever network-console is involved; seeing that affect amd64 means I could try and run some commands locally without having to deal with arch-specific environments. It seems crypt() is no longer declared as it used to, and we get implicit function declaration warnings from gcc, which later explains the segfault at runtime. The declaration is guarded by __USE_MISC but #define'ing it doesn't seem to be sufficient. I've decided to add a <crypt.h> include, which seems to do the trick: gen-crypt no longer segfaults, and seems to return suitable results on my amd64 machine: kibi@armor:~/debian-installer/packages/network-console$ ./gen-crypt foo $1$g.dM....$EJhR11EsVD5jY1Smnomsc0A Source uploaded to the archive (1.81), then it'll get picked up by the buildds[1] and later made available in daily builds. It'd be nice if you could double check that the runtime within d-i is also fine. 1. https://buildd.debian.org/status/package.php?p=network-console&suite=sid Thanks again for the report & follow-ups (und vielen Dank zu Marc for the initial forward from the user list). Cheers, -- Cyril Brulebois (k...@debian.org) <https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant
signature.asc
Description: PGP signature