sscanf was not causing the segfault. The additional columns creates a different less obvious bug.
The real problem in this bug is that there are now IRQs greater than 2299, but MAX_IRQS in sleepd.h is 255. I have verified that increasing this value stops this segfault. This brings up the following questions: 1. Do any of the interrupts > 255 relate to user activity? They are for the graphics, ethernet, and ahci devices on my system. Those are not keyboard/mouse activity that this section of code was looking for. 2. What is the largest interrupt that we will see? The two possible solutions are ignore any interrupts > MAX_IRQS or increase MAX_IRQS. Would anyone care to give me a recommendation about which option is better? I am leaning toward ignoring higher interrupts to save memory. Maybe I should make it not use the array key as a dictionary. Thank you. -- Segmentation fault on start https://bugs.launchpad.net/bugs/371463 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
