From: hollerer@gmx.net
To: gdb@sourceware.cygnus.com
Subject: gdb m68k remote debugging - unwanted program stop after 24 lines console output
Date: Tue, 18 Apr 2000 01:40:00 -0000 [thread overview]
Message-ID: <38FC1F40.FB4B7D45@gmx.net> (raw)
hi,
i have a little question which i hope you can answer.
host: linux, m68k-gdb-aout 4.18
target: motorola 68332, m68k-stub.c
remote debugging via rs232
i have wrapped the output of the target into a 'O' message.
this works fine. but the host gdb stops the program after
24 lines of output with the message:
---Type <return> to continue, or q <return> to quit---
can i avoid this? it's ok that the output would get lost.
but the program should not be stopped.
thx for any answer
franz hollerer
--
Austria
Usually we don't have kangaroos.
From msalter@cygnus.com Tue Apr 18 01:55:00 2000
From: Mark Salter <msalter@cygnus.com>
To: hollerer@gmx.net
Cc: gdb@sourceware.cygnus.com
Subject: Re: gdb m68k remote debugging - unwanted program stop after 24 lines console output
Date: Tue, 18 Apr 2000 01:55:00 -0000
Message-id: <200004180855.BAA06942@rtl.cygnus.com>
References: <38FC1F40.FB4B7D45@gmx.net>
X-SW-Source: 2000-04/msg00083.html
Content-length: 462
>>>>> hollerer writes:
> hi,
> i have a little question which i hope you can answer.
> i have wrapped the output of the target into a 'O' message.
> this works fine. but the host gdb stops the program after
> 24 lines of output with the message:
> ---Type <return> to continue, or q <return> to quit---
> can i avoid this? it's ok that the output would get lost.
> but the program should not be stopped.
Try "set height 0" in your .gdbinit file.
--Mark
next reply other threads:[~2000-04-18 1:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-18 1:40 hollerer [this message]
2000-04-18 3:50 ` Andrew Cagney
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=38FC1F40.FB4B7D45@gmx.net \
--to=hollerer@gmx.net \
--cc=gdb@sourceware.cygnus.com \
/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