summaryrefslogtreecommitdiff
path: root/datapath-windows/ovsext/Actions.c
diff options
context:
space:
mode:
authorAlin Gabriel Serdean <aserdean@ovn.org>2017-08-25 20:48:18 +0300
committerAlin Gabriel Serdean <aserdean@ovn.org>2017-09-01 23:58:45 +0300
commit44820d2aa972d522a02e0fd6291e1ca3f8314ee1 (patch)
treeb1efb7d8ad42e49ba8495f1cec3840673ecabb12 /datapath-windows/ovsext/Actions.c
parentc3a90b467a02140b27cd65b79f91db72fcbb266a (diff)
downloadopenvswitch-44820d2aa972d522a02e0fd6291e1ca3f8314ee1.tar.gz
daemon-windows: Set default error mode for services
Microsoft allows default process memory dumps via WER (Windows Error Reporting). WER can be set to collect dumps using in general using: https://msdn.microsoft.com/en-us/library/windows/desktop/bb787181(v=vs.85).aspx If a normal application crashes, the user will receive a pop-up dialog, in which he will be asked of his consent on what will be the steps after the dump was created (debug, close or send the dump to MSFT). We disable the dump creation via WER in: https://github.com/openvswitch/ovs/blob/master/lib/util.c#L492 because the idea is we don't want a pop-up if a OVS process (eg. ovs-vsctl) has crashed. (more information on the subject: https://blogs.msdn.microsoft.com/oldnewthing/20040727-00/?p=38323) Until we implement our own dump collection mechanism, we can set the default error mode for services because there are no pop-ups allowed in that case. Signed-off-by: Alin Gabriel Serdean <aserdean@ovn.org> Requested-by: Anand Kumar <kumaranand@vmware.com> Acked-by: Anand Kumar <kumaranand@vmware.com>
Diffstat (limited to 'datapath-windows/ovsext/Actions.c')
0 files changed, 0 insertions, 0 deletions