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

2016-09-15 Thread Dario Lombardo 
>
>
>>
> 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.
>

Good catch! It works for extcaps as well.
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

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

2016-09-13 Thread Pascal Quantin 
Hi Dario,

2016-09-13 15:26 GMT+02:00 Dario Lombardo :

> 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.
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe