[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kmail-devel
Subject:    Re: Bug#22749: SEGV in imap kioslave on Solaris
From:       Jan de Visser <jan_dv () yahoo ! com>
Date:       2001-03-21 18:21:28
[Download RAW message or body]

Did some poking around, and figured out that the problem is that basically
the following happends:

    QString foo;
    ...
    qDebug( "foo: %s", foo.latin1() );

When you delve into the qt code, instantiating a QString like this gives you
a string object with a NULL character buffer. latin1() then returns NULL as
well, and Solaris barfs on that.

So the question is:
1. Is that the wanted behaviour? I would think that 'QString foo' gives me
an empty string ("") not a NULL string.
2. Why does it work on Linux? Is Linus more forgiving here??

Jan.

==============================================================
Jan de Visser                     Digital Fairway Corp.
tel. (416) 628 7525               jdevisser@digitalfairway.com

          <Enter any 12 digit prime to continue>
==============================================================

----- Original Message -----
From: <jan_dv@yahoo.com>
To: <submit@bugs.kde.org>
Sent: Tuesday, March 20, 2001 10:02 AM
Subject: Bug#22749: SEGV in imap kioslave on Solaris


> Package: kmail
> Version: KDE 2.1.9 CVS/CVSup/Snapshot
> Severity: normal
> Installed from:    Compiled sources
> Compiler:          gcc 2.95.2
> OS:                Solaris
> OS/Compiler notes: SunOS york 5.8 Generic sun4u sparc SUNW,Ultra-5_10
>
> When trying to expand my IMAP folder list (clicking on the little '+'
sign), a msg box pops up saying 'The process for the imap://xxxx protocol
died unexpectedly'.
>
> Oh yeah, thing works fine under Linux (slack 7.1), and my server is fine
too, since other clients work without problem...
>
> Console (kioslave) output:
>
> kio (Slave): createSlave for imap://xxx;AUTH=*@xxx.com:143
> kio (KLauncher): requestSlave imap xxx.com
> kio (KLauncher): KLauncher::requestSlave for imap: looking for a slave
handling
> imap
> kio (KLauncher): KLauncher: launching new slave kio_imap4 with
protocol=imap
> kdeinit: Got EXEC 'kio_imap4' from klauncher.
> IMAP4::kdemain
> kio (KLauncher): kio_imap4 (pid 19093) up and running.
> kio (KLauncher): Slave launched, pid = 19093
> kio (KLauncher): requestSlave got pid 19093
> kio (Slave): PID of slave = 19093
> kmail: enable progress
> kio (Slave): slave has connected to application
> kio (Scheduler): scheduler: job started 336be8
> IMAP4::dispatch - command=48
> IMAP4::setHost - host= xxx.com, port= 143, user= xxx;AUTH=*, pass=
> xx
> IMAP4::setHost - host= xxx.com, port= 143, user= xxx;AUTH=*, auth=
>  *, pass=xx
> imapParser::parseLoop - unhandledResponse:
> * OK xxx.com IMAP4rev1 v12.250 server ready^M
>
> imapParser::parseLoop -  completed OK: CAPABILITY completed
> IMAP4: setHost: capability
> 'IMAP4'
> 'IMAP4REV1'
> 'NAMESPACE'
> 'IDLE'
> 'SCAN'
> 'SORT'
> 'MAILBOX-REFERRALS'
> 'LOGIN-REFERRALS'
> 'AUTH=LOGIN'
> 'THREAD=ORDEREDSUBJECT'
> IMAP4::dispatch - command=49
> IMAP4::makeLogin - checking login
> IMAP4::makeLogin - attempting login
> IMAP4::makeLogin - open_PassDlg: user=jan pass=xx
> imapParser::parseLoop -  completed OK: LOGIN completed
> IMAP4::makeLogin - login succeded
> kio (Slave): got answer 103
> IMAP4::dispatch - command=71
> IMAP4::listDir - imap://xxx%3BAUTH%3D*:xxx@xxx.com:143/
> imapParser::parseURL - imap://xxx%3BAUTH%3D*:xxxx@xxx.com:143/
> URL: box= , section= kioslave : ###############SEG FAULT#############
> kdeinit: PID 19093 terminated.
>
>
> (Submitted via bugs.kde.org)
>
> _______________________________________________
> Kmail Developers mailing list
> Kmail@master.kde.org
> http://master.kde.org/mailman/listinfo/kmail
>



_______________________________________________
Kmail Developers mailing list
Kmail@master.kde.org
http://master.kde.org/mailman/listinfo/kmail

[prev in list] [next in list] [prev in thread] [next in thread]