That's exactly what I was looking for! I don't even have to recompile Wireshark. ;) Thank you very much.
On Fri, Sep 18, 2009 at 11:38 AM, Jim Young <[email protected]> wrote: > Hello Beth, > > >>> Beth <[email protected]> 09/18/09 10:58 AM >>> > > As I try to debug my Lua issues, it would be really helpful if I could > view > > stdout while running the wireshark GUI. Then I can print debug info with > a > > simple printf instead of having to add gratuitous items to the display > tree. > > > > I thought all I would need to do is run wireshark from the command line, > but > > as soon as the GUI window opens the command line prompt returns > > immediately. Is there a way to keep it from doing that, so that stdout > > comes out in the command window? > > You haven't said what platform you are developing on, but perhaps > changing the Wireshark User Interface Preference of "Open a console > window" from the default on "Never" to "Automatic (advanced user)" > or even "Always (debugging)" would provide the console window you > desire. > > It works for me when working in C. > > I typically run my Wireshark instanaces with Console mode set to "Always". > If and when the console window is created, you will be required to also > click on and close the console the console window to completely shutdown > Wireshark. > > I hope this proves helpful. > > Jim Y. > > > ___________________________________________________________________________ > Sent via: Wireshark-dev mailing list <[email protected]> > Archives: http://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev > mailto:[email protected]?subject=unsubscribe >
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <[email protected]> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:[email protected]?subject=unsubscribe
