Qt-interest Archive, June 2007
Hi guys, very interesting fact happens to me
Message 1 in thread
I have an application that manipulate openGL surfaces; compiling it using qt
4.1.0 works fine;
compiling it with 4.3.0 it crashes with such a message:
a lot of
Warning: QWidget::repaint: Recursive repaint detected
Warning: QWidget::repaint: Recursive repaint detected
Warning: QWidget::repaint: Recursive repaint detected
Segmentation fault
Any idea for debugging?
Thanks in advence.
Cheers
--
[ signature omitted ]
Message 2 in thread
Try putting a break point in the QWidget::repaint code and looking at
the stack to see how its gotten recursive...
Most likely, your calling paint on a child widget directly
Scott
> -----Original Message-----
> From: Fabio Giovagnini [mailto:fabio.giovagnini@xxxxxxxxxxxxxxx]
> Sent: Wednesday, June 06, 2007 11:22 AM
> To: qt-interest@xxxxxxxxxxxxx
> Subject: Hi guys, very interesting fact happens to me
>
> I have an application that manipulate openGL surfaces; compiling it
using
> qt
> 4.1.0 works fine;
> compiling it with 4.3.0 it crashes with such a message:
> a lot of
>
> Warning: QWidget::repaint: Recursive repaint detected
> Warning: QWidget::repaint: Recursive repaint detected
> Warning: QWidget::repaint: Recursive repaint detected
> Segmentation fault
>
>
> Any idea for debugging?
>
> Thanks in advence.
>
> Cheers
>
>
> --
> Fabio Giovagnini
>
> Aurion s.r.l.
> via degli orti 11,
> 40050 Funo di Argelato (BO)
> P.I e C.F.
> 00885711200
> Tel. +39.335.8350919
> Fax +39.051.8659009
>
> www.aurion-tech.com
>
> account telefono VoIP skype (www.skype.com):
> aurion.giovagnini
>
> --
> To unsubscribe - send a mail to qt-interest-request@xxxxxxxxxxxxx with
> "unsubscribe" in the subject or the body.
> List archive and information: http://lists.trolltech.com/qt-interest/
--
[ signature omitted ]
Message 3 in thread
I'll try and I'll let you know.
Thanks a lot
Alle 20:29, mercoledì 6 giugno 2007, Scott Aron Bloom ha scritto:
> Try putting a break point in the QWidget::repaint code and looking at
> the stack to see how its gotten recursive...
>
> Most likely, your calling paint on a child widget directly
>
> Scott
>
> > -----Original Message-----
> > From: Fabio Giovagnini [mailto:fabio.giovagnini@xxxxxxxxxxxxxxx]
> > Sent: Wednesday, June 06, 2007 11:22 AM
> > To: qt-interest@xxxxxxxxxxxxx
> > Subject: Hi guys, very interesting fact happens to me
> >
> > I have an application that manipulate openGL surfaces; compiling it
>
> using
>
> > qt
> > 4.1.0 works fine;
> > compiling it with 4.3.0 it crashes with such a message:
> > a lot of
> >
> > Warning: QWidget::repaint: Recursive repaint detected
> > Warning: QWidget::repaint: Recursive repaint detected
> > Warning: QWidget::repaint: Recursive repaint detected
> > Segmentation fault
> >
> >
> > Any idea for debugging?
> >
> > Thanks in advence.
> >
> > Cheers
> >
> >
> > --
> > Fabio Giovagnini
> >
> > Aurion s.r.l.
> > via degli orti 11,
> > 40050 Funo di Argelato (BO)
> > P.I e C.F.
> > 00885711200
> > Tel. +39.335.8350919
> > Fax +39.051.8659009
> >
> > www.aurion-tech.com
> >
> > account telefono VoIP skype (www.skype.com):
> > aurion.giovagnini
> >
> > --
> > To unsubscribe - send a mail to qt-interest-request@xxxxxxxxxxxxx with
> > "unsubscribe" in the subject or the body.
> > List archive and information: http://lists.trolltech.com/qt-interest/
>
> --
> To unsubscribe - send a mail to qt-interest-request@xxxxxxxxxxxxx with
> "unsubscribe" in the subject or the body. List archive and information:
> http://lists.trolltech.com/qt-interest/
--
[ signature omitted ]
Message 4 in thread
On 06.06.07 20:21:48, Fabio Giovagnini wrote:
> I have an application that manipulate openGL surfaces; compiling it using qt
> 4.1.0 works fine;
> compiling it with 4.3.0 it crashes with such a message:
> a lot of
>
> Warning: QWidget::repaint: Recursive repaint detected
> Warning: QWidget::repaint: Recursive repaint detected
> Warning: QWidget::repaint: Recursive repaint detected
> Segmentation fault
>
>
> Any idea for debugging?
First thing to do would be: run the app in a debugger and when it
crashes produce a backtrace. That way you know where it crashes. Then
step through the problematic function and check the value of the
variables that are used.
Andreas
--
[ signature omitted ]