Petter Reinholdtsen <[EMAIL PROTECTED]> writes: > [Dan Griswold] >> With the new upgrade, the netplan daemon ate up all the memory on the >> system and caused the xserver and its associated tty to fail. This >> required a reboot. > > Hm. I'm not aware of any changes which could give this result. What > was the version number you used before this problem arrived?
That's what I thought when I looked in the changelog. I upgrade very frequently, so my replaced version must be the immediately previous one, 1.9-2. > Can you try to run the program using strace and valgrind, to see what > is going on? And perhaps run it under gdb to try to get a backtrace? strace doesn't appear to report much of value (although I could be mistaken). valgrind reports the following in its summary: ==23228== ERROR SUMMARY: 32 errors from 18 contexts (suppressed: 0 from 0) ==23228== malloc/free: in use at exit: 688 bytes in 20 blocks. ==23228== malloc/free: 91 allocs, 70 frees, 11206 bytes allocated. ==23228== For counts of detected errors, rerun with: -v ==23228== searching for pointers to 20 not-freed blocks. ==23228== checked 78356 bytes. ==23228== ==23228== LEAK SUMMARY: ==23228== definitely lost: 156 bytes in 11 blocks. ==23228== possibly lost: 0 bytes in 0 blocks. ==23228== still reachable: 532 bytes in 9 blocks. ==23228== suppressed: 0 bytes in 0 blocks. ==23228== Use --leak-check=full to see details of leaked memory. ==23049== ==23049== ERROR SUMMARY: 32 errors from 18 contexts (suppressed: 0 from 0) ==23049== malloc/free: in use at exit: 156 bytes in 11 blocks. ==23049== malloc/free: 73 allocs, 62 frees, 7858 bytes allocated. ==23049== For counts of detected errors, rerun with: -v ==23049== searching for pointers to 11 not-freed blocks. ==23049== checked 69632 bytes. ==23049== ==23049== LEAK SUMMARY: ==23049== definitely lost: 156 bytes in 11 blocks. ==23049== possibly lost: 0 bytes in 0 blocks. ==23049== still reachable: 0 bytes in 0 blocks. ==23049== suppressed: 0 bytes in 0 blocks. ==23049== Use --leak-check=full to see details of leaked memory. Several of the errors reported above that summary are "Conditional jump or move depends on uninitialised value(s)" I don't know what I'm doing with gdb, so I'll hold off until instructed further. Thank you so much for your help. Dan Griswold Rochester, NY -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
