Hi, On Sun, May 21, 2017 at 11:09:03PM +0200, Víctor Cuadrado Juan wrote: > On 21/05/17 22:05, Adam D. Barratt wrote: > > > > I've been unable to reproduce this using either jessie or sid's uscan > > (running on a jessie host, admittedly). I'd be interested if anyone else > > can reproduce this or if there's anything unusual about the machine. > > Seems that it isn't only present on uscan: while running debsign I get a > segmentation fault.
Have you checked hardware failure? Did you reinstall perl to be safe side? > I've carried out heavy tasks on the machine (compiling,etc), and apart > from this everything looks fine. Like compiling kernel in C code? debsign and uscan are perl code. Any of these regex tends to eat more memory but strange .... > I was able to reproduce it again on my workstation configuration deployed > into a fresh lxc container (using https://github.com/viccuad/salt-configs). > There, uscan consumes all the cpu until it gets killed by zsh, and debsign > the same. Why don't you create a new account with minimal customization and bash as login under a real machine. Let"s not complicate matter with lxc. Do you still suffer? Osamu
