> The symbols are loaded from the binary. You should compile the udeb you > wish to debug yourself (with debug information),
I tried to run "make main-menu" in the chroot sid environment and had problems with gcc3.3.something inside woody (gcc 2.95.4) I had to fix a couple of include paths and I managed to get the object files but had problems when linking because I don't have libdebconfclient and I don't know how to build it > Then run the installer and attach gdb to the running process. Perhaps you have to > insert some delay into the udeb's postinst code so that you have enough > time to attach and set breakpoints. > Attach like this gdb $UDEB $PID, where $UDEB is the unstripped > executable (gdb loads symbols from it) and $PID is the process id of the > running process. I _think_ I'm not that far from it.... thanx for your help Sebastian maybe somebody on this list will have some spare time to send me such a log... please! ciao d. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
