Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: Elena Zannoni <ezannoni@cygnus.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] Multiarch tm_print_insn
Date: Wed, 05 Sep 2001 11:58:00 -0000	[thread overview]
Message-ID: <15254.30646.484902.681604@krustylu.cygnus.com> (raw)
In-Reply-To: <Pine.SUN.3.91.1010905131249.13798C-100000@is>

Eli Zaretskii writes:
 > 
 > On Wed, 5 Sep 2001, Elena Zannoni wrote:
 > 
 > > How about this?
 > 
 > Approved, with a few minor comments (see below).
 > 
 > Thanks!
 > 
 > > +debugged memory abd returns the length of the instruction, in bytes.  If
 >                    ^^^
 > A typo.

OK

 > 
 > > +a target doesn't define its own printing routine, it defaults to an
 > > +accessor function for the global pointer @var{tm_print_insn}.
 > 
 > Isn't tm_print_insn a name of a real variable in GDB sources?  If so,
 > it should have the @code markup; @var is for names of formal
 > parameters and such likes: names that stand for something else, not
 > for themselves.
 >

Ok, thanks.
 
 > > +usually points to a function in the @code{opcodes} library
 > > +(@xref{,,opcodes}).
 > 
 > Does opcodes have a manual?  I cannot find it anywhere.  If there is
 > no docs for opcodes, I think we should remove the xref.
 > 

There is a section about opcodes in this same document.


 > >  @var{info} is a structure defined in @code{opcodes}
 > > +used to pass information to the instruction decoding routine.
 > 
 > Maybe we should at least tell what is the name of that structure, so
 > that an interested reader could grep for it in opcodes' sources.

True will do.

How about this:

Index: gdbint.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdbint.texinfo,v
retrieving revision 1.35
diff -u -p -r1.35 gdbint.texinfo
--- gdbint.texinfo	2001/08/15 14:47:53	1.35
+++ gdbint.texinfo	2001/09/05 18:57:42
@@ -3566,6 +3566,18 @@ If non-zero, the target has support for 
 watchpoints.  @xref{Algorithms, watchpoints}, for more details and
 other related macros.
 
+@item TARGET_PRINT_INSN (@var{addr}, @var{info})
+@findex TARGET_PRINT_INSN
+This is the function used by @value{GDBN} to print an assembly
+instruction.  It prints the instruction at address @var{addr} in
+debugged memory and returns the length of the instruction, in bytes.  If
+a target doesn't define its own printing routine, it defaults to an
+accessor function for the global pointer @code{tm_print_insn}. This
+usually points to a function in the @code{opcodes} library (@ref{Support
+Libraries, ,Opcodes}).  @var{info} is a structure (of type
+@code{disassemble_info}) defined in @file{include/dis-asm.h} used to
+pass information to the instruction decoding routine.
+
 @item USE_STRUCT_CONVENTION (@var{gcc_p}, @var{type})
 @findex USE_STRUCT_CONVENTION
 If defined, this must be an expression that is nonzero if a value of the


  reply	other threads:[~2001-09-05 11:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-21 16:26 Elena Zannoni
2001-08-21 17:33 ` Andrew Cagney
2001-09-05 17:07   ` Elena Zannoni
     [not found] ` <3405-Wed22Aug2001084554+0300-eliz@is.elta.co.il>
     [not found]   ` <15236.12258.330506.371048@krustylu.cygnus.com>
     [not found]     ` <9003-Thu23Aug2001085323+0300-eliz@is.elta.co.il>
2001-09-04 21:00       ` Elena Zannoni
2001-09-05  3:12         ` Eli Zaretskii
2001-09-05 11:58           ` Elena Zannoni [this message]
2001-09-06  0:47             ` Eli Zaretskii
2001-09-06  5:02               ` Elena Zannoni

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=15254.30646.484902.681604@krustylu.cygnus.com \
    --to=ezannoni@cygnus.com \
    --cc=eliz@is.elta.co.il \
    --cc=gdb-patches@sources.redhat.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