After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 112799 - GLib GError console output
GLib GError console output
Status: RESOLVED DUPLICATE of bug 106409
Product: dia
Classification: Other
Component: win32
0.91
Other Windows
: Normal blocker
: ---
Assigned To: Steffen Macke
Dia maintainers
Depends on:
Blocks:
 
 
Reported: 2003-05-12 00:33 UTC by Julian Suggate
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Julian Suggate 2003-05-12 00:33:15 UTC
First of all, you guys rule for even attempting this port, and you doubly 
rule for doing it so well.

But I have to mention, what's up with the obscenely high level of console 
output?

You guys could make the product exactly 6.923103 octillion times more 
usable and 3.862325 pentillion times faster, if you could just suppress 
all that superfluous output!

Do you realise how many processor cycles you are giving to the System Idle 
Process because of all your blocking on I/O to the screen? Jeepers!

Please please please stop GLib from outputting all those silly error 
messages, I can hardly USE the program.


+murkj
Comment 1 Steffen Macke 2003-05-12 03:55:01 UTC
The symptoms are different, but the cause is the same:
Mixing of c-runtimes.MSVC 7 doesn't allow to link against
MSVCRT.DLL
Hopefully this problem will be fixed in one of the next
releases.

*** This bug has been marked as a duplicate of 106409 ***
Comment 2 Julian Suggate 2003-05-12 04:48:37 UTC
I'm not proposing that you fix the *cause* of the errors (mixed c-
runtimes), because that'll take ages and you are obviously working on 
that anyway.

But what about a quick fix for now, while you work on the major issue?

While there are so many errors, it must be possible to *suppress* the 
output so that at least there aren't so many calls to printf(). This 
may not fix the underlying problems, but it WOULD make the program 
HEAPS faster

Then I could convince my boss to donate to you guys!

doable?