[Bug 155157] "Unknown Error" when using HTTP or POP3 KIO slave

[Jon]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=155157         




------- Additional Comments From SchaduwBlink hotmail com  2008-01-10 03:18 -------
I was able to get a little further into the debugging process. After making starting kdeinit4 with the command I listed in the previous posting, I came to the debug part of the output after typing in www.kde.org. Normally in previous tasks, I just pressed c for continue and I didn't get very far. However, after pressing c once, I I then started to press n for next and I got a bit further into the code. This is the output:

(gdb) break QTcpSocket::waitForConnected()
Function "QTcpSocket::waitForConnected()" not defined.
Breakpoint 1 (QTcpSocket::waitForConnected()) pending.

(gdb) c
Continuing.

Program received signal SIGSTOP, Stopped (signal).
[Switching to Thread 0xa65f76d0 (LWP 18306)]
0xa7ef0410 in __kernel_vsyscall ()

(gdb) n
Single stepping until exit from function __kernel_vsyscall, 
which has no line number information.

Program received signal SIGSTOP, Stopped (signal).
0xa7ef0410 in __kernel_vsyscall ()

(gdb) n
Single stepping until exit from function __kernel_vsyscall, 
which has no line number information.
0xa68befb6 in kill () from /lib/libc.so.6

(gdb) n
Single stepping until exit from function kill, 
which has no line number information.
launch (argc=4, _name=0x807ae64 "kio_http", args=0x807aed9 "", cwd=0x0, envc=0, envs=0x807aede "", reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x80511e1 "0") at /var/tmp/portage/kde-base/kdelibs-9999.4/work/kdelibs-9999.4/kinit/kinit.cpp:615

(gdb) n
[New Thread 0xa631db90 (LWP 18427)]

Program received signal SIGINT, Interrupt.
0xa7ef0410 in __kernel_vsyscall ()

It was here when konq reuturned that that error message that I keep getting. Insight was in some kind of processing loop and would not return. I had to press the stop button in order to gain control back. I have a screenshot of the of insight code part. This is the last thing of code right when Konq returns the error. I should have screenshoted the previous page maybe.
http://img149.imageshack.us/my.php?image=insight5no9.png
Here it would not return at all. You see the stop button? Is the code in some kind of infinite loop that is keeping insight from returning after executing that? After returning I decided to press n again to see what would happen, but it's just pop commands indicating that the function is exiting.

(gdb) n
Single stepping until exit from function __kernel_vsyscall, 
which has no line number information.
0xa6968511 in select () from /lib/libc.so.6

(gdb)

Does any of this output help?