Hi there.
Can anyone else reproduce the problem?
I could create a simple c++ program and compiled+linked it with the same
flags as sbt2sbd-d and I could debug it just fine even with the old
global options, so it's not just the one thing.
Regards,
Philip Ashmore
--
To UNSUBSCRIBE, email to
I switched back to using Sid - the problem's still there.
Philip
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Ok, I think I've nailed it (but we've been here before ;).
It looks like there were some breakpoints set in the applications kdbgrc
file that gdb didn't like, and kdbg couldn't grok gdbs repsonses.
I tracked it down by writing a gdb wrapper (attached).
It tee's gdb output to a text file.
Hi there.
There was a global options setting I'd made years ago.
gdb --fullname --nx -d /v3c/dev/debian/src
That directory doesn't exist any more.
Setting it to
gdb --fullname --nx
seems to have solved it - I can debug once again.
I could still be wrong about this.
Since kdbg
On Wed, Sep 19, 2012 at 11:26:53PM +0100, Philip Ashmore wrote:
It went away shortly after I reported the bug - now it's back.
I'm using Debian/Sid and keep my packages current daily so I think
one update fixed it and then another one broke it again.
I now wish I had reported it as fixed
Hi there.
I just tried debugging the same program with Wheezy in VMware Player -
it works fine so it looks like something in Sid.
I'm running Trinity but I don't think that's the problem as kdbg used to
work.
I had to rebuild the package and its dependencies because of the older
It turns out that the VMware image I was testing with was an older
Wheezy/sid image.
I did a fresh VMware install with debian-wheezy-DI-b2-amd64-netinst.iso
and guess what? I'm getting the same problem!
Go figure.
Sorry about the mis-information.
Philip
--
To UNSUBSCRIBE, email to
It went away shortly after I reported the bug - now it's back.
I'm using Debian/Sid and keep my packages current daily so I think one
update fixed it and then another one broke it again.
I now wish I had reported it as fixed so that the problem package(s)
could have been pinned down more
8 matches
Mail list logo
