[Dan Griswold] > 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 verify this by installing the old binary package and see if it get rid of the problem? <URL:ftp://ftp.debian.org/debian/pool/main/p/plan/netplan_1.9-2_i386.deb> > strace doesn't appear to report much of value (although I could be > mistaken). Probably right. Can you try with ltrace? > valgrind reports the following in its summary: [...] > Several of the errors reported above that summary are "Conditional > jump or move depends on uninitialised value(s)" Those are the ones I am interested in. But it would be more useful if the binary was compiled with debugging symbols included. I'm not sure about your skill profile, so I make a stepwise list of instructions. apt-get source plan cd plan-1.9 debuild make -C src clean linux DEBUG=-g valgrind src/netplan If I got this right, you should have a netplan binary compiled with debug information, and run it under valgrind. > I don't know what I'm doing with gdb, so I'll hold off until > instructed further. Use the same binary as above, and run these commands: gdb src/netplan break exit run # It should now stop when exit() is called bt The output from the 'bt' command should be the backtrace at the point were it exits. > Thank you so much for your help. Thank you for your patience. I hope we can figure this one out. I had a look at the code, and have no idea how your problem could have been introduced by the recent changes. Do you have any special netplan configuration? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
