Hi Jason,
I've reproduced the log file below. I don't know how to
interpret this, do you see anything wrong in the log fie?
On Oct 8, 2010, at 5:17 PM, Jason Wessel wrote:
>
> If you add the following to your .gdbinit it will at least tell you what
> happened at the end.
>
> set remotelogfile /tmp/gdb_serial_log.txt
w +$qSupported#37
r +$#00
w +$Hg0#df
r +$OK#9a
w +$?#3f
r +$S05#b8
w +$Hc-1#09
r +$OK#9a
w +$qC#b4
r +$QC00000000fffffffe#43
w +$qAttached#8f
r +$#00
w +$qOffsets#4b
r +$#00
w +$g#67
r
+$140000009301008001000000844ec7c0acf16fc067000000010000000700000000e823cf00e823cf930100209301004028de58c0b0de58c0749409c0849409c00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000093010040#aa
w +$mc0099484,4#a2
r +$ffdeffe7#fd
w +$mc0099480,4#9e
r +$5ff07ff5#69
w +$mc0099484,4#a2
r +$ffdeffe7#fd
w +$mc0099480,4#9e
r +$5ff07ff5#69
w +$mc0099484,4#a2
r +$ffdeffe7#fd
w +$mc0099484,4#a2
r +$ffdeffe7#fd
w +$mc0099484,4#a2
r +$ffdeffe7#fd
w +$qSymbol::#5b
r +$#00
w +
c cd /tool/patches/android-rowboat-froyo-2.2-patchwork/kernel
c info proc
End of log
> It would be good to know if eclipse timed out and it just detached from
> the target, or if some command crashed gdb. It is purely a guess, but
> it is probably eclipse requesting lots of information and simply timing out.
>
>
> I would not expect the terminal session to crash. If an oops is
> printed, it means there is an internal kgdb problem.
I don't think kgdb crashed. It seems to be working reliably on the target side.
If I restart the debug session, it receives the sysreq + g command and starts
the debugger.
Best regards,
Elvis Dowson
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
