Bug#686312: kdbg can't start app

2012-09-22 Thread Philip Ashmore

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 debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#686312: kdbg can't start app

2012-09-22 Thread Philip Ashmore

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



Bug#686312: kdbg can't start app

2012-09-22 Thread Philip Ashmore

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.

Gdbs output is also attached, for reference.

I tried different versions of gdb from 7.5 back to 7.1a to see if any 
worked - the one I ran this test with was 7.5.


Regards,
Philip Ashmore
#!/bin/sh
/usr/local/bin/gdb $@ 21 | tee /v3c/bin/gdb-out.txt
GNU gdb (GDB) 7.5
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show copying
and show warranty for details.
This GDB was configured as x86_64-unknown-linux-gnu.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/.
(gdb) (gdb) (gdb) (gdb) (gdb) (gdb) (gdb) (gdb) (gdb) (kdbg)(kdbg)Reading 
symbols from /v3c/dev/autobook/storyboard/build/sb/.libs/sbt2sbd-d...done.
(kdbg)(kdbg)Working directory /v3c/dev/autobook/storyboard/build/sb/tests.
(kdbg)(kdbg)Breakpoint 1 at 0x404ea3: file ../../sb/sbt2sbd.cpp, line 122.
(kdbg)Breakpoint 2 at 0x405172: file /usr/include/v3c/string_utils.hpp, line 28.
(kdbg)Note: breakpoint 1 also set at pc 0x404ea3.
Breakpoint 3 at 0x404ea3: file ../../sb/sbt2sbd.cpp, line 122.
(kdbg)Note: breakpoint 2 also set at pc 0x405172.
Breakpoint 4 at 0x405172: file /usr/include/v3c/string_utils.hpp, line 28.
(kdbg)Breakpoint 5 at 0x7796e9a9
(kdbg)Breakpoint 6 at 0x7796ec30
(kdbg)Breakpoint 7 at 0x407594: file ../../sb/sbt2sbd.cpp, line 101.
(kdbg)Breakpoint 8 at 0x404e85: file ../../sb/sbt2sbd.cpp, line 118.
(kdbg)Note: breakpoints 1 and 3 also set at pc 0x404ea3.
Breakpoint 9 at 0x404ea3: file ../../sb/sbt2sbd.cpp, line 122.
(kdbg)Note: breakpoints 2 and 4 also set at pc 0x405172.
Breakpoint 10 at 0x405172: file /usr/include/v3c/string_utils.hpp, line 28.
(kdbg)Note: breakpoints 1, 3 and 9 also set at pc 0x404ea3.
Breakpoint 11 at 0x404ea3: file ../../sb/sbt2sbd.cpp, line 122.
(kdbg)Note: breakpoints 2, 4 and 10 also set at pc 0x405172.
Breakpoint 12 at 0x405172: file /usr/include/v3c/string_utils.hpp, line 28.
(kdbg)Note: breakpoints 1, 3, 9 and 11 also set at pc 0x404ea3.
Breakpoint 13 at 0x404ea3: file ../../sb/sbt2sbd.cpp, line 122.
(kdbg)Note: breakpoints 2, 4, 10 and 12 also set at pc 0x405172.
Breakpoint 14 at 0x405172: file /usr/include/v3c/string_utils.hpp, line 28.
(kdbg)Note: breakpoints 1, 3, 9, 11 and 13 also set at pc 0x404ea3.
Breakpoint 15 at 0x404ea3: file ../../sb/sbt2sbd.cpp, line 122.
(kdbg)Note: breakpoints 2, 4, 10, 12 and 14 also set at pc 0x405172.
Breakpoint 16 at 0x405172: file /usr/include/v3c/string_utils.hpp, line 28.
(kdbg)Note: breakpoints 1, 3, 9, 11, 13 and 15 also set at pc 0x404ea3.
Breakpoint 17 at 0x404ea3: file ../../sb/sbt2sbd.cpp, line 122.
(kdbg)Note: breakpoints 2, 4, 10, 12, 14 and 16 also set at pc 0x405172.
Breakpoint 18 at 0x405172: file /usr/include/v3c/string_utils.hpp, line 28.
(kdbg)Note: breakpoints 1, 3, 9, 11, 13, 15 and 17 also set at pc 0x404ea3.
Breakpoint 19 at 0x404ea3: file ../../sb/sbt2sbd.cpp, line 122.
(kdbg)Note: breakpoints 2, 4, 10, 12, 14, 16 and 18 also set at pc 0x405172.
Breakpoint 20 at 0x405172: file /usr/include/v3c/string_utils.hpp, line 28.
(kdbg)Note: breakpoints 1, 3, 9, 11, 13, 15, 17 and 19 also set at pc 0x404ea3.
Breakpoint 21 at 0x404ea3: file ../../sb/sbt2sbd.cpp, line 122.
(kdbg)Note: breakpoints 2, 4, 10, 12, 14, 16, 18 and 20 also set at pc 0x405172.
Breakpoint 22 at 0x405172: file /usr/include/v3c/string_utils.hpp, line 28.
(kdbg)Note: breakpoints 1, 3, 9, 11, 13, 15, 17, 19 and 21 also set at pc 
0x404ea3.
Breakpoint 23 at 0x404ea3: file ../../sb/sbt2sbd.cpp, line 122.
(kdbg)Note: breakpoints 2, 4, 10, 12, 14, 16, 18, 20 and 22 also set at pc 
0x405172.
Breakpoint 24 at 0x405172: file /usr/include/v3c/string_utils.hpp, line 28.
(kdbg)Note: breakpoints 1, 3, 9, 11, 13, 15, 17, 19, 21 and 23 also set at pc 
0x404ea3.
Breakpoint 25 at 0x404ea3: file ../../sb/sbt2sbd.cpp, line 122.
(kdbg)Note: breakpoints 2, 4, 10, 12, 14, 16, 18, 20, 22 and 24 also set at pc 
0x405172.
Breakpoint 26 at 0x405172: file /usr/include/v3c/string_utils.hpp, line 28.
(kdbg)Note: breakpoints 1, 3, 9, 11, 13, 15, 17, 19, 21, 23 and 25 also set at 
pc 0x404ea3.
Breakpoint 27 at 0x404ea3: file ../../sb/sbt2sbd.cpp, line 122.
(kdbg)Note: breakpoints 2, 4, 10, 12, 14, 16, 18, 20, 22, 24 and 26 also set at 
pc 0x405172.
Breakpoint 28 at 0x405172: file /usr/include/v3c/string_utils.hpp, line 28.
(kdbg)Note: breakpoints 1, 3, 9, 11, 13, 15, 17, 19, 21, 23, 25 and 27 also set 
at pc 0x404ea3.
Breakpoint 29 at 0x404ea3: file ../../sb/sbt2sbd.cpp, line 122.
(kdbg)Note: breakpoints 2, 4, 10, 12, 14, 16, 18, 20, 22, 24, 26 and 28 also 
set at pc 0x405172.
Breakpoint 30 

Bug#686312: kdbg can't start app

2012-09-21 Thread Philip Ashmore

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 sometimes worked with it and sometimes it didn't, I'll leave 
it to Ana to look into it a bit more rather than closing it myself.


Regards,
Philip Ashmore


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#686312: kdbg can't start app

2012-09-20 Thread Ana Guerrero
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 so that the problem package(s)
 could have been pinned down more easily.
 
 I'm pretty sure that a package caused (then fixed, then caused) this
 problem.
 


Thanks Philip.
The bug was filed while I was in holidays and I still haven't gotten
the chance to look at it. I will try in the next 2 weeks.

Ana


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#686312: kdbg can't start app

2012-09-20 Thread Philip Ashmore

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 
tools+compiler in Wheezy as they're older than the ones I use to build 
it in Sid.


If you want the sources for the program (sbt2sbd), it's part of my 
v3c-storyboard package in SourceForge which I will be releasing in a few 
weeks but I can email you tarballs of it and its dependent packages in 
their current state if you need them.


Philip


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#686312: kdbg can't start app

2012-09-20 Thread Philip Ashmore
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 debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#686312: kdbg can't start app

2012-09-19 Thread Philip Ashmore

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 easily.


I'm pretty sure that a package caused (then fixed, then caused) this 
problem.


Philip


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org