ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-dev: Re: [Wireshark-dev] g_print & co on Windows

From: Bill Meier <wmeier@xxxxxxxxxxx>
Date: Tue, 13 Sep 2016 11:07:05 -0400
On 9/13/2016 9:31 AM, Pascal Quantin wrote:
Hi Dario,

2016-09-13 15:26 GMT+02:00 Dario Lombardo <dario.lombardo.ml@xxxxxxxxx
<mailto:dario.lombardo.ml@xxxxxxxxx>>:

    Hi
    I'm debugging sshdump on windows and I found an unexpected behavior
    with glib logging functions.

    g_error: seems to work. A popup appears and program stops
    g_warning: nothing, with or without G_MESSAGES_DEBUG=all
    g_debug: same as above
    g_print: nothing printed

    I recall something about those functions not working on windows, but
    I can't find a pointer in the ML archives. Is is a known bug on
    glib? Or something missing on my side?


You can find some analysis done by Bill a few years ago explaining why
it is a mess: https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6695#c2

Cheers,
Pascal.




I seem to remember that when starting Wireshark on Windows from the command line that I had to redirect stdout and stderr to files to see the output.