summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar http://nullroute.eu.org/~grawity/ <Mantas@web>2013-11-13 06:22:49 +0000
committerGravatar admin <admin@branchable.com>2013-11-13 06:22:49 +0000
commit4d14b14a7fb81ae99bf8decd0fd440da4c04815b (patch)
tree3ca6d67501a58c34b04edc0dcdec5dff9564d4f1
parentb962715e38f188cb8c5ace47d6645d91f2270cef (diff)
Added a comment
-rw-r--r--doc/devblog/day_55__fireside_porting/comment_1_d690a52db82f9594d99ae65fe51e1f1a._comment8
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/devblog/day_55__fireside_porting/comment_1_d690a52db82f9594d99ae65fe51e1f1a._comment b/doc/devblog/day_55__fireside_porting/comment_1_d690a52db82f9594d99ae65fe51e1f1a._comment
new file mode 100644
index 000000000..74acc8322
--- /dev/null
+++ b/doc/devblog/day_55__fireside_porting/comment_1_d690a52db82f9594d99ae65fe51e1f1a._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="http://nullroute.eu.org/~grawity/"
+ nickname="Mantas"
+ subject="comment 1"
+ date="2013-11-13T06:22:49Z"
+ content="""
+[ProcExp](http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx) may be useful -- it can show process-related syscalls and their return codes _(among other things like file or registry access)_ so it should tell exactly why the exec failed.
+"""]]