[Wireshark code review <code-review-do-not-reply@xxxxxxxxxxxxx>]

URL: https://code.wireshark.org/review/gitweb?p=wireshark.git;a=commit;h=83c17c4d1724264627b7369fc3ac1968d780be02
Submitter: "Peter Wu <peter@xxxxxxxxxxxxx>"
Changed: branch: master
Repository: wireshark

Commits:

83c17c4 by Jaap Keuter (jaap.keuter@xxxxxxxxx):

    Allow trace of sync spawns
    
    When Wireshark uses a synchronous spawn (e.g., to launch an extcap)
    it would be nice to be able to see what command line is constructed
    to launch the process, and to see what comes back. The output will
    go to the g_log.
    
    Change-Id: Iec6baeebc026cd80398084c9644fc916ab068e2f
    Reviewed-on: https://code.wireshark.org/review/30475
    Petri-Dish: Dario Lombardo <lomato@xxxxxxxxx>
    Tested-by: Petri Dish Buildbot
    Reviewed-by: Peter Wu <peter@xxxxxxxxxxxxx>
    

Actions performed:

    from  e7bd315   XRA: Bugfix in ncp_profile_select
     add  83c17c4   Allow trace of sync spawns


Summary of changes:
 wsutil/ws_pipe.c | 46 +++++++++++++++++++++++++++++++++++++---------
 1 file changed, 37 insertions(+), 9 deletions(-)