From 51253d5af24316560cf098706e8e8616d7c9dd8a Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 4 Feb 2015 14:44:35 -0400 Subject: comment --- .../comment_1_e982f985e5ca57454725e9e9a482e30c._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/bugs/git-annex_died_of_signal_11_when_syncing_content/comment_1_e982f985e5ca57454725e9e9a482e30c._comment diff --git a/doc/bugs/git-annex_died_of_signal_11_when_syncing_content/comment_1_e982f985e5ca57454725e9e9a482e30c._comment b/doc/bugs/git-annex_died_of_signal_11_when_syncing_content/comment_1_e982f985e5ca57454725e9e9a482e30c._comment new file mode 100644 index 000000000..f81f1d732 --- /dev/null +++ b/doc/bugs/git-annex_died_of_signal_11_when_syncing_content/comment_1_e982f985e5ca57454725e9e9a482e30c._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2015-02-04T18:38:09Z" + content=""" +Well, a signal 11 can be caused by several different things, including +some messed up pointer stuff in a C library, or just bad memory on your +computer. I think a memory test would be a good first step. + +If the memory checks clean, running git-annex in gdb and getting a stack +trace after a crash may help. +"""]] -- cgit v1.2.3