This is the mail archive of the guile@cygnus.com mailing list for the guile project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: debugging dynamically linked modules


>>>>> "Klaus" == Klaus Schilling <Klaus.Schilling@home.ivm.de> writes:

Klaus> What is a viable method to debug dynamically loaded modules? gdb can't find
Klaus> their symbols before they are loaded, so one can't set breakpoints etc. before
Klaus> running guile.

I usually put a breakpoint at `main', hit run, and when stopping at
main, I can now set other breakpoints since the libraries has been
linked in. When restarting the debugged process, gdb will temporarily
disable the breakpoints in shared libraries and automagically enable
them when the library is in place.

The alternative is to link guile statically (use something like
`--with-shared=no' to configure). If guile is the only program using
libguile, there isn't really anything gained from making it shared.


---------------------------+--------------------------------------------------
Christian Lynbech          | Telebit Communications A/S                       
Fax:   +45 8628 8186       | Fabrik 11, DK-8260 Viby J
Phone: +45 8628 8177 + 28  | email: chl@tbit.dk --- URL: http://www.telebit.dk
---------------------------+--------------------------------------------------
Hit the philistines three times over the head with the Elisp reference manual.
                                        - petonic@hal.com (Michael A. Petonic)