Stephen J. Turnbull wrote: BTW, I've just discovered that I also can run gdb, contrary to what I had thought first. What I hadn't noticed is that after the "Cannot access memory at adress xxx" message, the program is in fact running :-/ This actually has something to do with dynamic loading, as demonstrated by this excerpt of a gdb session: ,---- | (gdb) run | Starting program: /usr/local/src/dxemacs/src/xemacs -nw -vanilla | Cannot access memory at address 0x40016e08 | (gdb) where | #0 0x4000cca4 in _dl_debug_state () from /lib/ld-linux.so.2 | (gdb) cont | Continuing. | Cannot access memory at address 0x40016e08 | (gdb) where | #0 0x4000cca4 in _dl_debug_state () from /lib/ld-linux.so.2 | (gdb) cont `----- after that, everything goes well ... -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / EPITA / LRDE mailto:didier＠lrde.epita.fr /_/ / /_/ / /__ / 14-16 rue Voltaire Tel. +33 (1) 53 14 59 47 94276 Kremlin-Bicêtre cedex Fax. +33 (1) 44 08 01 99