If you want to be a software developer the task you're amiming at is providing the users you like to have with properly functioning software. As far as I can see for now you're quite some miles away from that. I'm really sorry, as I liked abiword until now, but I probably change to some stable program instead. Sorry you missed, pal.
On Mon, 22 Jun 2009 12:43:58 +0200 Patrik Fimml <pat...@fimml.at> wrote: > On Mon, Jun 22, 2009 at 12:20:35PM +0200, subhuman wrote: > > > 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 > > I did, in one of my earlier mails. > > > > 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. > > Correct. Just wanted to be sure. > > > > > > > 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. > > No. I asked for a gdb backtrace from an executable compiled with > debugging symbols, which has all sorts of additional information, like > exactly where the execution stopped (not as memory address, but traced > back to the source code). > > The backtrace generated by glibc on double-free is not nearly as useful. > > > 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. > > Go ahead, then, come up with a patch! > > > And furthermore: since I've been helping you for four or five days > > doing your work now I guess it's really your turn. > > Well, *if* you really are a "retired programmer", then it's a shame for > you that you haven't been able to provide me with a proper backtrace for > five days now. > > > 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. > > Do my job? It's not that I get paid for this. > > And even if it was my job: Sorry, I can't just go over to your place, > look at the problem, and then start debugging. As I cannot reproduce the > bug here, I have to rely on you to provide me enough information. > > Apparently, you're not willing to cooperate, which is your good right of > course. But never complain again about not being able to print from > abiword. > > > Patrik > -- 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