[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[GNUnet-SVN] [gnunet] branch master updated: doc: gnunet-c-tutorial: don
From: |
gnunet |
Subject: |
[GNUnet-SVN] [gnunet] branch master updated: doc: gnunet-c-tutorial: done? |
Date: |
Wed, 06 Sep 2017 10:12:12 +0200 |
This is an automated email from the git hooks/post-receive script.
ng0 pushed a commit to branch master
in repository gnunet.
The following commit(s) were added to refs/heads/master by this push:
new 706017af1 doc: gnunet-c-tutorial: done?
706017af1 is described below
commit 706017af17667401fb5d555fc9b789a2525eb642
Author: ng0 <address@hidden>
AuthorDate: Wed Sep 6 08:11:56 2017 +0000
doc: gnunet-c-tutorial: done?
---
doc/gnunet-c-tutorial.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/gnunet-c-tutorial.texi b/doc/gnunet-c-tutorial.texi
index 46ad98480..880364444 100644
--- a/doc/gnunet-c-tutorial.texi
+++ b/doc/gnunet-c-tutorial.texi
@@ -1122,7 +1122,7 @@ running @command{configure}. More details about logging
can be found under
@uref{https://gnunet.org/logging}.
You should also probably enable the creation of core files, by setting
address@hidden, and echo'ing 1 into @file{/proc/sys/kernel/core\_uses\_pid}.
address@hidden, and echo'ing @code{1} into
@file{/proc/sys/kernel/core\_uses\_pid}.
Then you can investigate the core dumps with @command{gdb}, which is often
the fastest method to find simple errors.
--
To stop receiving notification emails like this one, please contact
address@hidden
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [GNUnet-SVN] [gnunet] branch master updated: doc: gnunet-c-tutorial: done?,
gnunet <=