Bug 157428

Summary: kbuildsycoca4 fails after compiling kdebase on Windows with emerge tool
Product: [Unmaintained] kde-windows Reporter: Christoph Watzl <christoph.watzl>
Component: buildsystemAssignee: Christian Ehrlicher <Ch.Ehrlicher>
Status: RESOLVED WORKSFORME    
Severity: crash    
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Microsoft Windows   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Verbose task list ('tasklist /v')

Description Christoph Watzl 2008-02-08 15:25:08 UTC 
Version:            (using Devel)
Installed from:    Compiled sources
Compiler:          gcc (GCC) 3.4.5 (mingw special) 
OS:                MS Windows

I've compiled kdebase on Windows with the 'emerge' tool, following the steps on >>http://techbase.kde.org/Getting_Started/Build/KDE4/Windows/emerge<<. However, when emerge tries to run kbuildsycoca4 as last step, or I try to run it manually, it crashes, giving the following output:

---
C:\KDE>kbuildsycoca4
create process "C:\KDE\bin\dbus-daemon.exe" "C:\KDE\bin\dbus-daemon.exe"  --se
ion
3764: assertion failed "(error) == NULL || dbus_error_is_set ((error))" file "
\kde-mingw\tmp\dbus-src-1.1.2.20071228\work\dbus\dbus\dbus-sysdeps-win.c" line
035 function _dbus_get_autolaunch_address
Backtrace:
4       KiFastSystemCallRet
3       WaitForSingleObject+0x12
3       dbus_print_backtrace+0x94
3       dbus_abort+0xb
3       dbus_real_assert+0x46
3       dbus_get_autolaunch_address+0x2b3
3       dbus_transport_open+0x540
3       dbus_transport_open+0x10e
3       dbus_connection_close+0x46b
3       dbus_bus_register+0x64f
3       ZN15QDBusConnection12connectToBusENS_7BusTypeERK7QString+0x203
3       ZN15QDBusConnection10sessionBusEv+0x82
3       ZN19KApplicationPrivate4initEb+0x14e
3       ZN12KApplicationC1Eb+0x22e
3       kdemain+0x10f5
2       kbuildsycoca4.exe+0x132a
2       kbuildsycoca4.exe+0x1247
2       kbuildsycoca4.exe+0x1298
3       RegisterWaitForInputIdle+0x49

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
---

When I try to run any KDE app such as KWrite, it also crashes, but I guess this is caused by kbuildsycoca4 failing. When I run e.g. kwrite.exe, I get a Windows popup error message titled "Microsoft Visual C++ Runtime Library":
---
Runtime Error!

Program: C:\KDE\bin\kwrite.exe

This application has requested the Runtime to terminate in an unusual way.
Please contact the application's support team for more information.
---
Comment 1 matthias sweertvaegher 2008-02-08 17:06:21 UTC 
did you run kbuildsycoca4 with all kde processes shut down? otherwise it doesn't get a lock.
Comment 2 Christoph Watzl 2008-02-08 17:29:51 UTC 
Created attachment 23479 [details]
Verbose task list ('tasklist /v')
Comment 3 Christoph Watzl 2008-02-08 17:31:41 UTC 
Oops, I meant to write a comment to the above attachment - well, killing all processes that didn't seem important didn't help. In the attachment of the previous comment is the list of all processes I had running.
Comment 4 Christoph Watzl 2008-02-08 17:41:42 UTC 
Just some additional info that I forgot: I'm running Windows XP Professional 32-bit on an Intel Core 2 Duo processor, and I'm using an account with administrator privileges (I know how that sucks :-)).
Comment 5 Christian Ehrlicher 2008-02-08 21:37:54 UTC 
Sorry, can't reproduce it on a clean win xp with mingw. You're using mingw, right? Do you maybe use your own mingw installation instead the one from emerge?

Please rebuild dbus with emerge:
emerge dbus-src

and try again.
Comment 6 Christoph Watzl 2008-02-09 02:07:31 UTC 
w00t! Now it works! Actually, I had an old standalone MinGW installation which I've been using with eclipse CDT in the past - this may have caused some kind of conflict with the MinGW installation that was installed via emerge. So I uninstalled the old MinGW and did 'emerge dbus-src' as you suggested; afterwards everything worked fine. The sad thing is that I can't tell which of the two steps was actually necessary ... 
Anyway, thanks for your patience with me! :-)
Comment 7 Christian Ehrlicher 2008-02-09 10:23:57 UTC 
Fne that it works now but it doesn't solve our problem - you're now using a self - compiled dbus instead our binaries. That's fine for you but isn't manageable for all :)
Is it possible to do some debug testing on your system? If yes, let me know.

Thx
Comment 8 Christian Ehrlicher 2008-02-09 10:38:51 UTC 
Another question. Was C:\KDE\bin\dbus-daemon.exe available before you installed dbus-src ?
Comment 9 Christoph Watzl 2008-02-09 15:04:44 UTC 
As for your second question: I can't really tell, now that it's there, but I could try it again with a clean installation. This will, of course, take some time. :-)
And to your first question: Sure, I have a lot of time at the moment. Feel free to e-mail me at any time (BTW, I'm German speaking :-)).
Comment 10 Christoph Watzl 2008-02-09 18:57:24 UTC 
After doing a clean rebuild of everything (I deleted my old KDE directory), I couldn't reproduce the problem any more. I really can't tell what the trouble was.
Comment 11 Christian Ehrlicher 2008-02-10 17:00:38 UTC 
I think we found the problem:
There was an error in our win32libs python script to install also msvc libs. This was fixed recently

-->
svn up emerge
emerge --unmerge dbus-src --unmerge win32libs
emerge win32libs