| Log from running "nmake check" on Win64 build using VS2013. |
text/plain
|
2016-04-28 16:12:54 UTC |
14.41 KB |
no flags
|
Details |
| Fix memory leak in _dbus_replace_install_prefix() on success case on Windows. |
patch
|
2016-05-09 21:35:19 UTC |
756 bytes |
no flags
|
Details |
| Display thread id in _dbus_verbose to be able to see thread issues. |
patch
|
2016-05-10 15:02:59 UTC |
2.22 KB |
no flags
|
Details |
| On Windows make access to member 'refcount' of struct DBusBabysitter thread save. |
patch
|
2016-05-10 15:06:14 UTC |
3.79 KB |
no flags
|
Details |
| Prefix debug messages displayed with _dbus_verbose() with a timestamp. |
patch
|
2016-05-11 06:09:15 UTC |
1.38 KB |
no flags
|
Details |
| Follow up of commit 5bd460ecf027bb36ffd21d325739bb51df94521f |
patch
|
2016-05-11 06:10:23 UTC |
1.62 KB |
no flags
|
Details |
| Display thread id in _dbus_verbose to be able to see thread issues (update 1) |
patch
|
2016-05-12 20:34:01 UTC |
3.02 KB |
no flags
|
Details |
| Prefix debug messages displayed with _dbus_verbose() with a timestamp (update 1) |
patch
|
2016-05-12 20:34:49 UTC |
1023 bytes |
no flags
|
Details |
| On Windows make access to member 'refcount' of struct DBusBabysitter thread save (update 1) |
patch
|
2016-05-12 20:35:25 UTC |
3.51 KB |
no flags
|
Details |
| Eliminates a race condition accessing DBusBabysitter instance at startup of babysitter() on Windows. |
patch
|
2016-05-12 23:46:39 UTC |
1.37 KB |
no flags
|
Details |
| Fix memory leak issue in spawn code on Windows. |
patch
|
2016-05-12 23:47:42 UTC |
3.36 KB |
no flags
|
Details |
| Fix memory leak issue in spawn code on Windows (update 1) |
patch
|
2016-05-12 23:53:50 UTC |
3.58 KB |
no flags
|
Details |
| Display thread id in _dbus_verbose to be able to see thread issues (update 2) |
patch
|
2016-05-13 13:03:09 UTC |
3.47 KB |
no flags
|
Details |
| dbus-spawn-win: Do not attempt to call child_setup (again) |
patch
|
2016-05-13 13:56:46 UTC |
921 bytes |
no flags
|
Details |
| Fix compiling on windows/mingw with automake build system. |
patch
|
2016-05-14 08:02:57 UTC |
721 bytes |
no flags
|
Details |
| Migrate platform specific spawn tests into cross platform tests. |
patch
|
2016-05-14 08:51:25 UTC |
16.19 KB |
no flags
|
Details |
| Migrate platform specific spawn tests into cross platform tests (update 1) |
patch
|
2016-05-14 08:58:28 UTC |
24.54 KB |
no flags
|
Details |
| Fix ambiguous setup of DBusBabySitter struct member child_handle on Windows. |
patch
|
2016-05-14 09:36:52 UTC |
1.17 KB |
no flags
|
Details |
| Fix memory leak issue in spawn code on Windows (update 2) |
patch
|
2016-05-14 09:43:00 UTC |
3.78 KB |
no flags
|
Details |
| Migrate platform specific spawn tests into cross platform tests (update 2) |
patch
|
2016-05-14 23:36:41 UTC |
24.52 KB |
no flags
|
Details |
| travis: compile with mingw in both production and debug flavours |
patch
|
2016-05-16 12:55:52 UTC |
978 bytes |
no flags
|
Details |
| test-segfault: add missing include of <stdio.h> on Windows |
patch
|
2016-05-16 13:33:35 UTC |
649 bytes |
no flags
|
Details |
| Migrate platform specific spawn tests into cross platform tests. |
patch
|
2016-05-16 13:35:58 UTC |
24.55 KB |
no flags
|
Details |
| Use mutex to protect access to DBusBabysitter struct members on Windows. |
patch
|
2016-05-17 14:39:24 UTC |
10.47 KB |
no flags
|
Details |
| Simplify windows implementation of _dbus_spawn_async_with_babysittery_sitter(). |
patch
|
2016-05-19 13:29:20 UTC |
13.91 KB |
no flags
|
Details |
| Simplify windows implementation of _dbus_spawn_async_with_babysittery_sitter() (update 1) |
patch
|
2016-05-20 06:46:00 UTC |
13.70 KB |
no flags
|
Details |
| Simplify windows implementation of _dbus_spawn_async_with_babysittery_sitter(). |
patch
|
2016-07-14 17:43:36 UTC |
13.00 KB |
no flags
|
Details |
| Simplify windows implementation of _dbus_spawn_async_with_babysittery_sitter(). |
patch
|
2016-07-14 18:07:42 UTC |
13.00 KB |
no flags
|
Details |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.