Oops. I forgot to mention: It's the M18 build running on Red Hat 6.9.5
(Pinstripe.)

"Raj Tanikella" <[EMAIL PROTECTED]> wrote in message
998csf$[EMAIL PROTECTED]">news:998csf$[EMAIL PROTECTED]...
> Hello All,
>
> I just tried running the gktEmbed example, and I'm seeing  to flavors of
> failure. Initially after compilation, I got the following result:
>
> [root@renoir mozilla]# /var/dev/mozilla/dist/bin/gtkEmbed
> Type Manifest File: /var/dev/mozilla/dist/bin/components/xpti.dat
> nsNativeComponentLoader: autoregistering begins.
> *** Registering nsSampleModule components (all right -- a generic module!)
>
> [A number of registrations, edited for brevity]
>
> *** Registering nsPluginModule components (all right -- a generic module!)
> *** Registering SimplePlugin components (all right -- a generic module!)
> *** Registering javascript: protocol components (all right -- a generic
> module!)*** Registering nsWidgetGTKModule components (all right -- a
generic
> module!)
> *** Registering Browser Embedding Module components (all right -- a
generic
> module!)
> nsNativeComponentLoader: autoregistering succeeded
> *** Deferring registration of sample JS components
> nNCL: registering deferred (0)
> *** Registering sample JS components
> nNCL: registering deferred (0)
> GFX: dpi=96 t2p=0.0666667 p2t=15 depth=24
> ###!!! ASSERTION: You can't dereference a NULL nsCOMPtr with
operator->().:
> 'mRawPtr != 0', file ../../../dist/include/nsCOMPtr.h, line 649
> ###!!! Break: at file ../../../dist/include/nsCOMPtr.h, line 649
> Segmentation fault
>
> Amid all this, I did see a window entitled "Embeddingi s fun!" which
> appeared and quickly disappeared. Subsequent invocations gave me the
> following:
>
> [root@renoir mozilla]# /var/dev/mozilla/dist/bin/gtkEmbed
> Assertion failure: (offset < reg->hdr.avail), at reg.c:1538
> Aborted (core dumped)
>
>
> I'm new to the Mozilla code (and projects of this size in general). I
would
> really appreciate it if someone could point me in the right direction as
to
> what I might do to rectify this. Is it a sign of a larger problem, or a
> simple fix?
>
> Thanks in advance.
>
> Raj Tanikella
>
>



Reply via email to