> That's a command to be typed at the gdb prompt, and the output of it is > what I am after.
You should have told me that > > Besides, you ran gdb as "gdb abiword": This will probably run the 2.6.8 > executable, and not the one we just compiled with debugging symbols. You > should give the full path, e.g. "gdb > /tmp/abiword-2.7.4-inst/bin/abiword" if you followed my original > instructions. I called gdb from the /tmp/... directory. so I assume gbd looked at the pwd first instead of guessing from the PATH environment variable. > > > > > Find gdb.txt attached > > > > > > Also, you don't need to attach both gdb.txt and the terminal output, > > > gdb.txt should suffice. I sent you the terminal output because it contained the backtrace you explicitly asked for. And for me as a sort of retired programmer I still can read a backtrace and figure out where the problem in question might come from. And furthermore: since I've been helping you for four or five days doing your work now I guess it's really your turn. It's definitely not my task as a user to do your job. We're just tearing on the same side of the rope, and it has been a pleasure so far helping you, but I guess I've torn the rope enough now. > > However, it seems now the ball is bouncing around on your side. You > > owe me a drink or two, u know? :-D > > Ah, that's a difficult matter. Maybe being able to print again will > settle that? ;-) > I shall prefer a Caipirinha. ;-) -- Volk ist Opium für die Religion. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
