[Qt-creator] qtc/gdb wooes

[André Pönitz]

On Mon, Feb 11, 2019 at 03:58:43PM +1300, Christian Gagneraud wrote:
> On Sat, 9 Feb 2019 at 09:53, André Pönitz <apoenitz at t-online.de> wrote:
> >
> > On Fri, Feb 08, 2019 at 11:27:56AM +1300, Christian Gagneraud wrote:
> > > Hi there,
> > >
> > > QtC is behaving very strangely when trying to debug a remote linux app.
> > > My qmake project is a very simple demo, i just have a main.cpp,
> > > application.cpp and mainwindow.cpp, cross compiled to arm-linux using
> > > custom toolchains, custom gdb too.
> > >
> > > When I insert a breakpoint, gdb doesn't stop on it. and QtC is lost.
> > > Clicking on the breakpoint in the debugger 'breakpoints' view gives me
> > > a error popup:
> > >
> > > Could not open ""/home/chgans/Projects/bolt-demos/embedded/mainwindow.cpp":48"
> > > for reading. Either the file does not exist or you do not have the
> > > permissions to open it.
> >
> > Please open a bug report at bugreports.qt.io and attach the debugger
> > log (Contents of right pane of Windows->Views->Debugger Log) taken
> > at a time when this breakpoint is not hit.
> 
> Thanks, see https://bugreports.qt.io/browse/QTCREATORBUG-21960
> 
> > > I checked the 'Global debugger log' view, but didn't find clue.
> > > Is there a way to activate some QtC internal logging?
> >
> > There is no extra debugger logging except for the debugger log.
> 
> That's a pity, i find it very hard to troubleshoot QtC when having
> issues related to gdb.
> And going through the "Global Debugger Logs" is not straight forward.
> Do you have a pretty-printer for these logs? There seems to be special
> markers in the first few columns

The special markers are for me to be able to grep such output more
comfortably.

Regarding the log content: There's usually enough in there to spot
typical setup problems. I am open for suggestions what to change,
but note that already now it can get huge, and parts are time
sensitive, so there's a limit to what can be done.

Andre'