On Thu, 16 Dec 2004, Andreas Aardal Hanssen wrote:
It shouldn't matter; Binc should handle corrupt files. But hmm.. just to make sure, you should try attaching to bincimapd after logging in using gdb (gdb <pid>), then reproduce the error so that gdb catches the crash. Then do a backtrace in gdb with "bt" to see where Binc crashes.
$ gdb 1254 GNU gdb 6.0 Copyright 2003 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i686-pc-linux-gnu"...1254: No such file or directory.
(gdb) bt
No stack.
(gdb)I don't have the "debug" USE flag on (because I don't know how to debug), but anyway the (gentoo) ebuild for bincimap doesn't make use of that flag. Should I compile binc by hand? (And do you think the big number of messages is not the issue?)
Jorge
