[Digikam-devel] Finding defect signals / slots

[Andi Clemens]

Also for me this alias doesn't work, I only get duplicate output in the 
console....

Andi

On Thursday 10 December 2009 23:30:59 Andi Clemens wrote:
> Why so long?
> A simple grep is enough, too :D
> 
> digikam 2>&1 | grep -i connect
> 
> Andi
> 
> On Thursday 10 December 2009 22:18:08 Gilles Caulier wrote:
> > great. i recommend to put this alias to HACKING file in svn.
> >
> > Gilles
> >
> > 2009/12/10 Johannes Wienke <languitar at semipol.de>:
> > > Hi @all,
> > >
> > > I've noticed from time to time that someone found a defect signal /
> > > slot connection, which can be somewhat annoying, because this issues
> > > only a warning on the command line. Here's a bash alias I created to
> > > track these errors. After the program terminates, it prints out errors
> > > concerning connections:
> > >
> > > alias digikamdbg="digikam 2>&1 | tee - /tmp/digikam.out; echo -e
> > > \"\n\n\nPossible connection errors:\n\n\"; cat /tmp/digikam.out | grep
> > > -A2 'Object::connect'"
> > >
> > > Maybe this helps to better tack these problems.
> > >
> > > Johannes
> > >
> > >
> > > _______________________________________________
> > > Digikam-devel mailing list
> > > Digikam-devel at kde.org
> > > https://mail.kde.org/mailman/listinfo/digikam-devel
> >
> > _______________________________________________
> > Digikam-devel mailing list
> > Digikam-devel at kde.org
> > https://mail.kde.org/mailman/listinfo/digikam-devel
> 
> _______________________________________________
> Digikam-devel mailing list
> Digikam-devel at kde.org
> https://mail.kde.org/mailman/listinfo/digikam-devel
>