X-Git-Url: http://info.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/blobdiff_plain/ac939f0ccce934321485e52c4d702fb29f881b86..df6fdd5cc2f67e7097e287bf8359809c1f943b08:/doc/doxygen/outcomes_logs.doc

diff --git a/doc/doxygen/outcomes_logs.doc b/doc/doxygen/outcomes_logs.doc
index 669b0e672b..131fe3655f 100644
--- a/doc/doxygen/outcomes_logs.doc
+++ b/doc/doxygen/outcomes_logs.doc
@@ -4,7 +4,7 @@
 
 Using @c printf or @c println to display information is possible, but
 quickly unpractical, as the logs of all processes get intermixed in
-your program's output. %As an answer, the SimGrid logging module allow
+your program's output. As an answer, the SimGrid logging module allow
 you to sort and filter the logs by emitter, by module and by gravity
 level. 
 
@@ -306,12 +306,6 @@ Here are the existing format directives:
  - %%L: line number where the log event was raised (LOG4J compatible)
  - %%M: function name (LOG4J compatible -- called method name here of course).
 
- - %%b: full backtrace (Called %%throwable in LOG4J).
-   Defined only under windows or when using the GNU libc because backtrace() is not defined
-   elsewhere, and we only have a fallback for windows boxes, not mac ones for example.
- - %%B: short backtrace (only the first line of the %%b).
-   Called %%throwable{short} in LOG4J; defined where %%b is.
-
  - %%d: date (UNIX-like epoch)
  - %%r: application age (time elapsed since the beginning of the application)