| Line 92: | Line 92: | ||
;[[/RoutingIdeas|General ideas about routing]] | ;[[/RoutingIdeas|General ideas about routing]] | ||
| − | == valgrind | + | == valgrind == |
| − | + | if you want to fix memory leaks, you can run valgrind with: | |
| + | |||
| + | valgrind --leak-check=full --track-origins=yes --num-callers=30 marble 2>&1 | tee MARBLE_MEMCHECK | ||
== Meetings == | == Meetings == | ||
Summaries and logs of scheduled Marble meetings can be found on the following pages: | Summaries and logs of scheduled Marble meetings can be found on the following pages: | ||
;[[/MarbleMeeting20081029|Wednesday Nov. 10th, 2008]] | ;[[/MarbleMeeting20081029|Wednesday Nov. 10th, 2008]] | ||
Languages: عربي | Asturianu | Català | Česky | Kaszëbsczi | Dansk | Deutsch | English | Esperanto | Español | Eesti | فارسی | Suomi | Français | Galego | Italiano | 日本語 | 한국어 | Norwegian | Polski | Português Brasileiro | Română | Русский | Svenska | Slovenčina | Slovenščina | српски | Türkçe | Tiếng Việt | Українська | 简体中文 | 繁體中文
Welcome!
Here you'll get all the information you need to start Marble development:
Here is some advice about how packaging is supposed to happen on the various plattforms that are supported.
Here are some tools and checks that are performed on marble code:
Here are a few links to various issues we are working on:
if you want to fix memory leaks, you can run valgrind with:
valgrind --leak-check=full --track-origins=yes --num-callers=30 marble 2>&1 | tee MARBLE_MEMCHECK
Summaries and logs of scheduled Marble meetings can be found on the following pages:
KDE TechBase 