On Fri, Aug 25, 2006 at 07:27:13PM +0200, Alexander Sack <[EMAIL PROTECTED]> 
wrote:
> On Fri, Aug 25, 2006 at 12:10:31PM -0500, Gerfried Fuchs wrote:
> > * Gerfried Fuchs <[EMAIL PROTECTED]> [2006-08-25 07:10]:
> > >  I'll try to clean up a bit more, it's more than those 117MB needed, the
> > > download would be 40MB itself...
> > 
> >  Finally finished to get the space ready, so here the bt with the -dbg
> > package installed is:
> > 
> > #v+
> > Program received signal SIGSEGV, Segmentation fault.
> > [Switching to Thread -1234422080 (LWP 16396)]
> > 0xb7ea6bd1 in GtkPromptService::PromptUsernameAndPassword ()
> >    from /usr/lib/kazehakase/libkazehakase.so.0
> > (gdb) bt
> > #0  0xb7ea6bd1 in GtkPromptService::PromptUsernameAndPassword ()
> >    from /usr/lib/kazehakase/libkazehakase.so.0
> > #1  0xb70f7eac in nsPrompt::PromptUsernameAndPassword (this=0x87433e0,
> >     dialogTitle=0x0, text=0x873b840, username=0xbfb7d7f4,
> >     password=0xbfb7d7f0, checkMsg=0xbfb7d624, checkValue=0x0,
> >     _retval=0xbfb7db10) at nsPrompt.cpp:325
> > #2  0xb7240232 in nsSingleSignonPrompt::PromptUsernameAndPassword (
> >     this=0x873cdf8, aDialogTitle=0x0, aText=0x873b840,
> >     aPasswordRealm=0xbfb7d9a8, aSavePassword=2, aUser=0xbfb7db0c,
> >     aPassword=0xbfb7db08, aConfirm=0xbfb7db10) at
> > nsSingleSignonPrompt.cpp:166
> 
> aDialogTitle is 0x0, which looks suspicious ...

It is not. nsSingleSignonPrompt::PromptUsernameAndPassword is called
from nsHttpChannel.cpp:2745 which is:
    rv = authPrompt->PromptUsernameAndPassword(nsnull, message.get(),
                                               key.get(),
                                               
nsIAuthPrompt::SAVE_PASSWORD_PERMANENTLY,
                                               &user, &pass, &retval);
See how aDialogTitle IS set to NULL.

Looking at kazehakase's code (GtkPromptService.cpp:343), aDialogTitle is
not the problem...

It would be nice to know on which line of GtkPromptService.cpp the crash
occurs. That would need a kazehakase debug build...

Anyway, it seems more obvious that the problem lies in kazahakase's
hands.

Mike


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to