[gentoo-user] OT - Good GUI debugger that can be used for Qt apps

[gentoo-user] OT - Good GUI debugger that can be used for Qt apps

[Michael Sullivan]

What's a good gui debugger that works on Qt c++ files?  I'm getting a
segmentation fault in my program and I don't really want to go through
each individual file (there are only eight, but I'm a wimp) and search
for it, because I lose track of which variables have been initialized
and which haven't.  I've tried to be careful this time, but at least one
crept through.  I'd like to be able to step through the program (without
waiting through the internal code of the Qt objects and find where this
problem is...

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] OT - Good GUI debugger that can be used for Qt apps

[Richard Fish]

On 11/20/05, Michael Sullivan <michael@espersunited.com> wrote:
> What's a good gui debugger that works on Qt c++ files?  I'm getting a

kdevelop

-Richard

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] OT - Good GUI debugger that can be used for Qt apps

[Michael Sullivan]

On Sun, 2005-11-20 at 14:19 -0700, Richard Fish wrote:
> On 11/20/05, Michael Sullivan <michael@espersunited.com> wrote:
> > What's a good gui debugger that works on Qt c++ files?  I'm getting a
> 
> kdevelop
> 
> -Richard

I copied my code into a KDevelop project and built it.  I then placed a
breakpoint on "int main (int argv, char** argc) and selected Start from
the Debug menu.  It immediately gave me a dialog that said "Program
received SIGABRT.  Aborted."  It did not tell me where my Segfault came
from.  Is there a way to get it to tell me, or at least allow me to step
through my program without instantly shutting down?

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] OT - Good GUI debugger that can be used for Qt apps

[Richard Fish]

On 11/20/05, Michael Sullivan <michael@espersunited.com> wrote:
> I copied my code into a KDevelop project and built it.  I then placed a
> breakpoint on "int main (int argv, char** argc) and selected Start from
> the Debug menu.  It immediately gave me a dialog that said "Program
> received SIGABRT.  Aborted."  It did not tell me where my Segfault came
> from.  Is there a way to get it to tell me, or at least allow me to step
> through my program without instantly shutting down?

That is very strange.  Did you build your program with the '-g'
(debug) option to gcc?

Also try "strace -s256 <programname>".  It will give you an idea of
what system calls your program is making at the time of the segfault,
and maybe give you a starting point of where to look in the code.

-Richard


>
> --
> gentoo-user@gentoo.org mailing list
>
>

-- 
gentoo-user@gentoo.org mailing list