Hi to all Kgdb developers, First let me say thank you for maintaining this great tool!
I able to use kgdb (over ethernet) for a few minutes every time and it works well in that period. After few minutes the debugger gets stuck, and so is the target machine. Mind you, I'm using an old kernel 2.6.32 (patched with kgdb-2.6.30). Will using a newer kernel and patch be any better? Is kgdboe reliability still an issue? If so, I have a suggestion - I'll post it in another email. Thank you! ------ Debugged machine: VM guest in ProxMox host CentOS 6 kernel: 2.6.32-358.el6.x86_64 with kgdb-2.6.30 patch applied manually eth0 is e1000 gcc version is gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-4) Client: Fedora 19 gdb version GNU gdb (GDB) Fedora 7.6.1-46.fc19 ------------------------------------------------------------------------------ Is your legacy SCM system holding you back? Join Perforce May 7 to find out: • 3 signs your SCM is hindering your productivity • Requirements for releasing software faster • Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce _______________________________________________ Kgdb-bugreport mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport
