Am Mittwoch, den 30.12.2009, 00:42 +0100 schrieb Andre Poenitz:
> On Tue, Dec 29, 2009 at 11:32:51PM +0100, Jochen Becher wrote:
> > Here is the complete debugger log after running to the first breakpoint:
> > [...]
> > >~"GNU gdb (GDB) 6.8.50.20081022-cvs\n"
>
> So you are running a 14 month old cvs snapshot of gdb? Why?
Because that's the version that was installed by MADDE. Of course the
standard gdb from Ubuntu is gdb 7.0-ubuntu. But MADDE (or the
integration of MADDE into qtcreator) seems to use the gdb from MADDE
which is that old cvs version - don't ask me why.
>
> > sSetze Haltepunkte...
> >
> > <19-break-list
> >
> > >19^done,BreakpointTable={nr_rows="0",nr_cols="6",hdr=[{width="7",alignment="-1",col_name="number",colhdr="Num"},{width="14",alignment="-1",col_name="type",colhdr="Type"},{width="4",alignment="-1",col_name="disp",colhdr="Disp"},{width="3",alignment="-1",col_name="enabled",colhdr="Enb"},{width="10",alignment="-1",col_name="addr",colhdr="Address"},{width="40",alignment="2",col_name="what",colhdr="What"}],body=[]}
> >
> > <20-break-insert -f "\"main.cpp\":8"
> >
> > >20^done,bkpt={number="1",type="breakpoint",disp="keep",enabled="y",addr="0x0000a5bc",func="main(int,
> > > char
> > >**)",file="main.cpp",fullname="/home/jbecher/projects/qt/qt-creator-tests/maemo-test-1/main.cpp",line="8",times="0",original-location="\"main.cpp\":8"}
> >
> > dALL COMMANDS DONE; INVOKING CALLBACK
>
> So you set exactly one breakpoint.
Yes, I did so. I set one breakpoint at the very first statement in
main(). But it doens't change anything if I set more breakpoints - only
that first breakpoint is hit - any other breakpoint is ignored.
>
> > [...]
> >
> > >*running,thread-id="all"
> >
> > >*stopped,reason="breakpoint-hit",disp="keep",bkptno="1",frame={addr="0x0000a5bc",func="main",args=[{name="argc",value="1"},{name="argv",value="0xbec49714"}],file="main.cpp",fullname="/home/jbecher/projects/qt/qt-creator-tests/maemo-test-1/main.cpp",line="8"},thread-id="1",stopped-threads="all"
>
> And it is hit... Fine.
>
>
> Initialization of the 'debugging helpers' fails:
> > >&"call (void*)dlopen(\"/home/user/libgdbmacros.so\", 0x00002)\n"
> > >~"\nProgram received signal "
> > >~"SIGSEGV, Segmentation fault.\n"
> > >~"0x00014a90 in malloc ()
> > from
> > /home/jbecher/.madde/0.5/sysroots/fremantle-qt-arm-sysroot-0942/lib/ld-linux.so.3\n"
> >
> > [...]
> > sAusgabe-Hilfsbibliothek-Initialisierung: No symbol "__dlopen" in
> > current context.
> > [...]
> > sDie Ausgabe-Hilfsbibliothek konnte nicht gefunden werden.
>
> That's not nice, but should not affect the breakpoints.
> However, it's unusual that it fails in 'malloc'...
That's true. I do not understand that either - if I run the program
without debugger it does not fail. I am not sure if it really breaks in
malloc - The yellow arrow points at the breakpoint in main(), only the
stack contents shows something from malloc().
>
> I'd try to use some "supported" version of gdb. That's basically a
> either a "plain" gdb 6.8 or any recent build of archer-tromey-python.
Ok, I will try to use the "official" MADDE way of debugging first - may
be it is a problem of MADDE instead of the integration into qtcreator.
>
> If that does not help, switch off the 'Debugging Helpers' (in the
> Debugger options, or in the context menu of the Locals and Watchers
> view) and check whether this makes a difference.
I will try it. Thank you,
jochen
>
> Regards,
> Andre'
> _______________________________________________
> Qt-creator mailing list
> [email protected]
> http://lists.trolltech.com/mailman/listinfo/qt-creator
_______________________________________________
Qt-creator mailing list
[email protected]
http://lists.trolltech.com/mailman/listinfo/qt-creator
