On 04/11/12 20:00, Johannes Sixt wrote:
Am 04.11.2012 00:04, schrieb Philip Ashmore:
Please find attached kdbg.txt that I obtained when I ran
kdbg -t kdbg.txt build/sb/sb-designer/.libs/sb-designer
Thanks!
One problem is that KDbg does not understand the response "Note:
breakpoints 4 and 5 also set at pc 0x41f0ce." This ultimately leads to
the accumulation of many breakpoints each time the session is started.
This one's even more bizarre - I get to main but can't step into a
function several levels down.
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.
Are those two "??()" entries in the stack trace normal?
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?
The next time it happens I'll build kdbg from source and apply the patch.
It doesn't happen often - but when it does it's a real pain.
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".
Recently I set a breakpoint and I saw <MULTIPLE> in the breakpoints list.
I've gotten into the habit of removing breakpoints that look like
they're going to cause problems,
so bear with me, I'm almost ready to release my stuff, so it might be a
few days.
Regards,
Philip
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
