I am trying to track it down, but am having a hard time. Every time I try and get a back trace no matter how many different dbgsym packages I install there always seems to be parts for which I don't have symbols, and they all appear to be in the thread that is being accused of the stack smash.
The first thing I did is do an ldd on the gpilotd binary and got dbgsym packages for all of the resulting files (well their packages.) Can anyone suggest a better way of trying to track this down. I'm happy to do the legwork, because I want it fixed. I am just having a hard time getting started. I am going to keep plugging away, but if someone can give me some guidance I would gladly accept it. -- [feisty] etodo conduit times out when syncing with a palm device https://bugs.launchpad.net/bugs/81170 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
