Bug#1022113: gpm: division by 0 in processMouse()

2022-12-06 Thread Jakub Wilk
* Axel Beckert , 2022-10-20 12:22: I wonder how to fix this properly? Setting opt_scaley hardcoded to 1 (or another sane value) in case it's 0 Yup, bumping opt_scaley from 0 to 1 should work. -- Jakub Wilk

Bug#1022113: gpm: division by 0 in processMouse()

2022-10-20 Thread Jakub Wilk
* Jakub Wilk , 2022-10-20 12:04: (which_mouse->opt_scaley)=(which_mouse->opt_scale)*50*maxx/80/maxy; If maxx is small and maxy is large (200 in my case), you could indeed end up with opt_scaley set to 0. Minor correction: my maxy is 56. (200 is my maxx on the days I'm not playing with

Bug#1022113: gpm: division by 0 in processMouse()

2022-10-20 Thread Axel Beckert
Control: tag -1 + upstream Control: forwarded -1 https://github.com/telmich/gpm/issues/45 Hi Jakub, Jakub Wilk wrote: > gpm crashes when I do "stty cols 1". […] > I think the culprit is the get_console_size() function, which does: > >

Bug#1022113: gpm: division by 0 in processMouse()

2022-10-20 Thread Jakub Wilk
Package: gpm Version: 1.20.7-10+b1 gpm crashes when I do "stty cols 1". GDB says: Program received signal SIGFPE, Arithmetic exception. 0x565eaf44 in processMouse (fd=5, event=0xff9a6980, type=0x565f73e0 , kd_mode=0) at daemon/processmouse.c:173 173 fine_dx %=