diff options
author | Jorge Arellano Cid <jcid@dillo.org> | 2009-11-06 21:04:10 -0300 |
---|---|---|
committer | Jorge Arellano Cid <jcid@dillo.org> | 2009-11-06 21:04:10 -0300 |
commit | 40990e657e7cbe660294e6edab6dc371555a3b14 (patch) | |
tree | 0f6d17d94750e31e3c93e3b84c3ce73cc1ac8d9b | |
parent | efd9b39150f607eba3725507ecb97a259871ec67 (diff) |
Added more tips in Dpid.txt
-rw-r--r-- | doc/Dpid.txt | 28 |
1 files changed, 25 insertions, 3 deletions
diff --git a/doc/Dpid.txt b/doc/Dpid.txt index bb5af2f6..3fb3cf3c 100644 --- a/doc/Dpid.txt +++ b/doc/Dpid.txt @@ -279,9 +279,31 @@ started. Once you've played enough with it, start reading the well commented code in hello.c and start making changes! - ------ - Notes: - ------ + + --------------- + Debugging a dpi + --------------- + + The simplest way is to add printf() feedback using the MSG* +macros. You can start the dpid by hand on a terminal to force +messages to go there. + + Sometimes more complex dpis need more than MSG*. In this case +you can use gdb like this. + + 1.- Add an sleep(20) statement just after the dpi starts. + 2.- Start dillo and issue a request for your dpi. This will + get your dpi started. + 3.- Standing in the dpi source directory: + ps aux|grep dpi + 4.- Take note of the dpi's PID and start gdb, then: + (gdb) attach <PID> + 5.- Continue from there... + + + ------------ + Final Notes: + ------------ 1.- If you already understand the hello dpi and want to try something more advanced: |