Message: previous - next
Month: May 2012

Re: [trinity-devel] Narrowed Time Frame 3/29->4/3 kwrite crash -> Looks like Qt3 bug

From: /dev/ammo42 <mickeytintincolle@...>
Date: Tue, 1 May 2012 23:15:14 +0200
On Tue, 01 May 2012 16:04:18 -0500
"David C. Rankin" <drankinatty@...> wrote:

> On 05/01/2012 02:34 PM, Timothy Pearson wrote:
> > I have not yet tried to replicate this bug on any systems here.
> > You said you are running this in a VirtualBox session, correct?  If
> > so, be aware that I have run into "TDE bugs" (crashes) before that
> > actually turn out to be VirtualBox bugs...
> >
> > Tim
> Yes,
>    That's why I was comforted that this wasn't the case when Darrell
> ran into it on a real box. So while the virtualbox variable is
> something to be aware of, it has real box confirmation as well. I'm
> guessing that it was tqt base on the first backtrace I caught today:
> 0xb69ebb20 in __x86.get_pc_thunk.bx ()
> from /opt/tqt3/lib/ (gdb) bt
> #0  0xb69ebb20 in __x86.get_pc_thunk.bx ()
> from /opt/tqt3/lib/ #1  0xb6a12d77 in category (c=...)
> at ../include/private/qunicodetables_p.h:99 #2  0xb6d89361 in isSpace
> (ch=...) at tools/qunicodetables_p.h:218
>    I have no idea what a 'get_pc_thunk.bx' is other than I thunk I'll
> get another pc too to speed up building :)  I guess it is talking
> about the bx register...
It loads the position of the calling code in the %ebx register:
>    That's why I just reported and pointed out the part
> of the crash at the top (which looked like it pointed to tqt3 to me
> -- that's just me guessing though)
>    I've read through the patch list, and again today in the 3/29 -
> 4/3 timeframe. I don't see anything that looks related by title
> either, but I don't know what all is getting changed.  We'll keep
> picking on it.