On Fri, Oct 3, 2014 at 10:16 PM, Tomasz Moń <deso...@gmail.com> wrote: > On Fri, Oct 3, 2014 at 5:17 PM, <mman...@netscape.net> wrote: >> Console App written in C(++) and not have the ugly console window pop up >> when you start >> capturing. >> >> If these are indeed "intended limitations", than yes documenting on the Wiki >> would be a good start. > > This is the way how it works in Windows. > > If you want to get rid of that console window you can change the > application type to Windows application (the difference is just one > byte in PE header). This will get your application to start without > standard handles (stdin, stdout, stderr). This is what I am going to > do in USBPcapCMD sometime soon.
gspawn-win32-helper.c has a nice comment about this issue: /* We build gspawn-win32-helper.exe as a Windows GUI application * to avoid any temporarily flashing console windows in case * the gspawn function is invoked by a GUI program. Thus, no main() * but a WinMain(). We do, however, still use argc and argv tucked * away in the global __argc and __argv by the C runtime startup code. */ ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
