On Fri, Dec 26, 2014, at 12:45 AM, Vadim Zhukov wrote:
> 2014-12-26 2:33 GMT+03:00 Adam Wolk <adam.w...@koparo.com>:
> > On Fri, Dec 26, 2014, at 12:15 AM, Vadim Zhukov wrote:
> > First of all thanks for the reply. I'm trying my best to help out and I
> > hope I'm not spamming.
> > If I should remove the CC to KDE porters then please inform me.
> 
> No, no, no, everyting is normal. The reality is that I'm 95% of "KDE
> development team" as of now, and also I'm responsible for Qt5 as well.
> The "KDE team" is just my hope that someone will pick up my work when
> I'll be hit by bus. :)
> 
> > Here are some follow ups that I found after investigating more since my
> > last email.
> >
> > 1. The double free crashes happen in 2 cases.
> >  a) trying to resize the window
> >  b) closing a modal dialog
> >
> > 2. While debugging one of the core dumps with gdb - gdb core dumped
> > itself
> >  I have this core dump set aside in case it's meaningful to someone.
> 
> GDB can't debug real Qt5 apps. :( That comes from old binutils here in
> OpenBSD, at least, and that's not a thing I can fix, sorry.
> 

Not a problem, just pointing things out as I hit them :)
If there is a soul still versed in gdb internals then that person can
hit me up
to get those core dumps and binaries that resulted in them.

> > 3. The browser itself works. I can load pages (ie. openbsd.org) open
> > tabs, close tabs etc.
> >
> > Here are the backtraces:
> >
> > 1) GDB core dump while debugging a core dump (this is while trying to
> > resize the whole window)
> >
> > 2) backtrace from dialog close
> 
> I have another report about bugs in Qt5WebKit. It's New Year coming
> here in Russia; hope to have time to debug those things during
> holidays. I understand those crashes are not pretty looking, but there
> is some other urgent stuff in Qt land as well. :-\
> 
> --
>   WBR,
>   Vadim Zhukov
> 

You already helped :) All I wanted to know is if those crashes are stuff
that
I'm doing wrong or a known/unknown issue in the Qt port.

I'll wait for new packages in the ports and will keep retrying / pin
pointing the issue.

Regards,

Reply via email to