Jay Lan wrote: > Jason Wessel wrote: >> You do have to make sure you issued the sysrq-g before you connect. To >> debug such issues you need to also execute the following command prior >> to issuing the "target remote ...". > > I specified "kgdbwait" instead. > >> set debug remote 1 >> >>> Has anyone seen this problem before? The kernel was 2.6.26-rc2 and >>> kgdb source was from kgdb-next about 3 weeks ago. >>> >>> >> I have only seen this sort of behavior if the kernel is not in "kgdb >> mode" when you connect. > > I tried "telnet 128.162.244.107 7003" from another window, and the > terminal server returned: > > Trying 128.162.244.107... > Connected to 128.162.244.107. > Escape character is '^]'. > > * > * * * ttyS3 is being used by (pid=20843) !!! > * > > 1 - Initiate a regular session > 2 - Initiate a sniff session > 3 - Send messages to another user > 4 - Kill session(s) > 5 - Quit > > Enter your option : > > Looks like the Cyclades terminal server does not allow > more than one application to access the same port?
Hi Jason, Just want to let you know that after my sysadmin reconfigured the terminal server, kgdboc worked here now. Thanks again. Regards, - jay > > Thanks for helping me diagnose the problem. > > Regards, > - jay > ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Kgdb-bugreport mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport
