This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug gdb/19841] remote debug via serial port not successful


https://sourceware.org/bugzilla/show_bug.cgi?id=19841

--- Comment #3 from Pedro Alves <palves at redhat dot com> ---
Your logs show:

...
"r r]putpkt: Junk: r[e]e[a]a[d]d[c]c[h]h[a]a[r]r[:]:[ ]
[I]I[n]n[p]p[u]u[t]t[/]/[o]o[u]u[t]t[p]p[u]u[t]t[ ] [e]e[r]r[r]r[o]o[r]r[\n]
[R]R[e]e[m]m[o]o[t]t[e]e[ ] [s]s[i]i[d]d[e]e[ ] [h]h[a]a[s]s[ ]
[t]t[e]e[r]r[m]m[i]i[n]n[a]a[t]t[e]e[d]d[ ]
[c]c[o]o[n]n[n]n[e]e[c]c[t]t[i]i[o]o[n]n[.].[ ] [ ] "
...

"putpkt: Junk: " indicates that the following characters are what it received
on the gdb protocol serial port.  However, we can tell that that's actually 
gdbserver output:

 readchar: Input/output error
 Remote side has terminated connection.

How did that manage to end up in gdb's serial traffic log?  It sounds like your
target is sending gdbserver stdout/stderr to /dev/ttyS0 too?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]