From: Pierre Muller <muller@cerbere.u-strasbg.fr>
To: "Sashan Govender" <sashang@hotmail.com>
Cc: gdb@sourceware.cygnus.com
Subject: Re: The debuggee's output
Date: Tue, 22 Aug 2000 03:38:00 -0000 [thread overview]
Message-ID: <200008221037.MAA13197@cerbere.u-strasbg.fr> (raw)
At 12:06 22/08/00 , you wrote:
>I've been debugging gdb5 with gdb5 in an attempt to figure out how it works
>and, more specifically, how gdb handles output from the inferior/debuggee. I
>can't find the functions that take care of this. Please could some one
>explain how it works.
GDB does nothing with debuggee's output.
On basic system as Dos this will for instance result in a mixing of GDB
output and
the debuggee output on screen.
On other system, you can define another screen output for the debuggee,
which avoid this mess.
(see "set tty" command on linux or
"set new-console" on cygwin win32)
But this doesn't change what I said above, GDB does not interfere with the
debuggee's
output (be it on screen, to a file or whatever else...)
unless you set some breakpoint, watchpoint or tracepoint on
the procedure that do this in the debuggee.
There might of course be some exceptions, like if the debuggee
tries to write over a file opened by GDB itself, but this should normally
not happen.
Pierre Muller
Institut Charles Sadron
6,rue Boussingault
F 67083 STRASBOURG CEDEX (France)
mailto:muller@ics.u-strasbg.fr
Phone : (33)-3-88-41-40-07 Fax : (33)-3-88-41-40-99
From benoit.millot@cstelecom.com Tue Aug 22 04:17:00 2000
From: "Benoit MILLOT" <benoit.millot@cstelecom.com>
To: "Peter.Schauer" <Peter.Schauer@regent.e-technik.tu-muenchen.de>, "gdb@sourceware.cygnus.com" <gdb@sourceware.cygnus.com>
Subject: Re: About GDB user-defined commands ?
Date: Tue, 22 Aug 2000 04:17:00 -0000
Message-id: <39A26231.4006C605@cstelecom.com>
References: <200008211711.TAA15504@reisser.regent.e-technik.tu-muenchen.de>
X-SW-Source: 2000-08/msg00103.html
Content-length: 1260
"Peter.Schauer" wrote:
> Try:
>
> define dm
> set var $taddr =3D $arg0
> set var $tsize =3D $arg1
> while $tsize !=3D 0
> if $tsize >=3D 10
> monitor dm $taddr $tsize
> set var $taddr =3D $taddr + 10
> set var $tsize =3D $tsize - 10
> else
> monitor dm $taddr $tsize
> set var $tsize =3D 0
> end
> end
> end
>
> > Hello,
> >
> > I want to develop a user-defined command for my own monitor
> > which i have already implemented into gdb with nomitor ops..
> >
> > Can i use a new variable? (answear seems to be NO)
> > Can i make operation (addition, ...) with input argument (arg0 ...)?
> >
> > Any ides will be appreciated.
> > Thanks.
> >
> --
> Peter Schauer pes@regent.e-technik.tu-muenchen.de
Thanks,
I have one problem more:
With this, on the serial line there is : dm $taddr $tsize instead=
of dm 407000 50
Monitor command pass arguments like string without interpretation ?
I want value on serial line.
But the command "monitor dm $arg0 $arg1" in a user-defined command works
fine,
on the serial line (dm 407000 50).
So what is the syntax for pass value instead of string with variable?
Thanks a lot.
Beno=EE=
t
next reply other threads:[~2000-08-22 3:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-22 3:38 Pierre Muller [this message]
2000-08-22 5:14 ` Eli Zaretskii
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=200008221037.MAA13197@cerbere.u-strasbg.fr \
--to=muller@cerbere.u-strasbg.fr \
--cc=gdb@sourceware.cygnus.com \
--cc=sashang@hotmail.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