Am 04.11.2012 22:17, schrieb Philip Ashmore: > On 04/11/12 20:00, Johannes Sixt wrote: >> The transcript does not show evidence that you even attempted to "step >> into" some functions. With the above deficiency in mind, the transcript >> and the screenshot look totally normal. > The segfault stopped execution. > I ran it a couple of times, I guess I didn't do stepping in the kdbg.txt > I attached. > I focussed on getting the transcript and the screen-shot straight after.
OK. > Are those two "??()" entries in the stack trace normal? They are not abnormal as far as KDbg is concerned. GDB reported these two stack frames, as you can see in the transcript. Whether you like what GDB produced, is an entirely different matter, of course ;-) > That Parser::parse() function is in the same project. >>> I don't know if this is a factor, but I renamed one of the files that >>> had breakpoints set for it >>> - No source file named project-file-treemodel.cpp. >> >> By itself, this does not cause the problem, but it adds to the symptoms, >> I think. >> >> The attached patch should cure the above-mentioned problem about >> "Note:...". Can you please test it? Do other problems mentioned in this >> bug report still occur? > Could you reply with a list of things to check after I've encountered > the problem and applied the patch? Most importantly, the list of breakpoints should not grow each time the session is loaded. But apart from that, I don't know what to watch out for. Message #5 reads "It worked a couple of times and now it can't reach main()". You should know what this means. I can only guess. > Any chance of adding > "remove all breakpoints" > "remove duplicate breakpoints at this address" > "remove duplicate breakpoints" > or maybe just remove duplicate breakpoints automatically at startup? > I nearly wore my poor mouse out clicking on "remove". Use your keyboard's autorepeat feature ;-) Click "View Code" and then keep your finger at F9 until the breakpoint goes away. > Recently I set a breakpoint and I saw <MULTIPLE> in the breakpoints list. This happens when you set a breakpoint in a constructor or destructor (and possibly others, perhaps inline or template functions). KDbg doesn't cope with these breakpoints. Erase them asap. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
