linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Ibon Gotxi Garcia <igotxi@jazzfree.com>
To: Linux PPC embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: kgdb and console output
Date: 14 Mar 2003 11:49:50 +0000	[thread overview]
Message-ID: <1047642589.367.19.camel@muse> (raw)


caution: perhaps a bit offtopic?

Hi all:

I'm still having problems to debug a kernel with kgdb:

both kgdb and console output go to /dev/ttyS0 (no chance of changing
that, we use the second serial port for other purposes). I get an
initial break in gdb (development machine), and the kernel loads
smoothly (outputs are perfect) till it reaches init, when the output
goes mad, repeating everything (but the first char) a number of times.
For example:

INIT: INIT: NIT: IT: T: : version 2.78 bootingersion 2.78 bootingrsion
2.78 bootingsion 2.78 bootingon 2.78 booting

and so on.

a.- Is that a gdb problem?
b.- Is it related with using the same serial port for both output and
debugging?
c.- Maybe i should change the tools i use in the root filesystem (aka
/bin/echo ...)?

I have tried not using colors or scape sequences to print, but a simple
echo "echo this" produces the same problem.
Any ideas?


Many regards.


--
Ibon Gotxi Garcia <igotxi@jazzfree.com>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2003-03-14 11:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-14 11:49 Ibon Gotxi Garcia [this message]
2003-03-14 17:25 ` kgdb and console output Tom Rini
2003-03-20 15:05   ` Ibon Gotxi Garcia
2003-03-20 15:09     ` Tom Rini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1047642589.367.19.camel@muse \
    --to=igotxi@jazzfree.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).