Date: Fri, 3 Jul 2020 14:45:58 +0530 From: Arka Sharma <arka.sw1988@gmail.com> To: Arka Sharma <arka.sw1988@gmail.com>, freebsd-hackers@freebsd.org Subject: Re: Hang while "Switching to gdb back-end" Message-ID: <CAPO=kN1NE-o82k3ABCeSa9F-gty_znb5N9r3bauSCQ%2Bh-Poe9g@mail.gmail.com> In-Reply-To: <CAPO=kN33%2BOYY1xYM28iUix4UB7hKEs6dL5e15TNS-yQ=utJXBA@mail.gmail.com> References: <CAPO=kN0fXcXd5ezLT7G=A5C=oSxOGbb4ODtvjMUx%2BJWOTC_LfQ@mail.gmail.com> <20200702163829.GA3431@x270> <CAPO=kN33%2BOYY1xYM28iUix4UB7hKEs6dL5e15TNS-yQ=utJXBA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Renamed the port from COM2 to COM1 is bios. This set the serial device to /dev/ttyu0. One more thing is previously I was terminating telnet using ctrl+] instead of that issued exit from the terminal (may be that resulted releasing /dev/ttyu0). With these two changes now I am able to connect kgdb. Regards, Arka On Thu, 2 Jul 2020, 23:22 Arka Sharma, <arka.sw1988@gmail.com> wrote: > Thanks for the reply. I have one more silly question. I have a terminal at > ttyu1 and I can login through telnet and it works fine except when I issue > "sysctl debug.kdb.enter=1" it hangs showing "debug.kdb.enter". I have > checked the freebsd handbook. At it is mentioned in chapter 26.6, I tried > to put "device sio" in my Kern Conf and it gives me build failure. Looking > at the build log it seems it is missing some header file while building > dev/sio.c. Basically I tried to get into db from serial console and failed. > One more thing is in the console after I get into db and launched gdb I > have also tried connecting kgdb from another host, but got timeout while > connecting the target. > > Regards, > Arka > > On Thu, 2 Jul 2020, 22:08 Navdeep Parhar, <nparhar@gmail.com> wrote: > >> On Thu, Jul 02, 2020 at 05:57:58PM +0530, Arka Sharma wrote: >> > Dear All, >> > >> > I have installed FreeBSD 12.1. I have set the "hint.uart.0.flags="0x90" >> in >> > the /boot/device.hints file. I also have both ddb and gdb listed when I >> > issue "sysctl debug.kdb.available". So when I launch db using "sysctl >> > debug.kdb.enter=1" and issue gdb to change the mode to gdb it shows >> > "Switching to gdb back-end" and doesn't respond to Ctrl+c. I have to >> reset >> > the system in order to get the system up. >> >> All this is expected behavior. You have to connect to the gdb backend >> over the serial port using kgdb running on a different system after you >> see the "Switching to gdb ..." message. Then debug as usual and detach >> when done. >> >> Regards, >> Navdeep >> >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPO=kN1NE-o82k3ABCeSa9F-gty_znb5N9r3bauSCQ%2Bh-Poe9g>