From: Elena Zannoni <ezannoni@redhat.com>
To: Fernando Nasser <fnasser@redhat.com>
Cc: Andrew Cagney <ac131313@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: RFC/RFA: Move new disassembler to libgdb proper
Date: Mon, 30 Sep 2002 09:44:00 -0000 [thread overview]
Message-ID: <15768.32428.867105.772361@localhost.redhat.com> (raw)
In-Reply-To: <3D98695A.5020406@redhat.com>
Just a thought. How about the TUI. Do we care about unifying its
disassemble with this one as well?
Elena
Fernando Nasser writes:
> Andrew Cagney wrote:
> > Two tweeks:
> >
> >> + /* Disassemble support for GDB.
> >> + Copyright 2000, 2001, 2002 Free Software Foundation, Inc.
> >> + Contributed by Cygnus Solutions (a Red Hat company).
> >
> >
> > The (C) should just be 2002 and ``Red Hat, Inc.''.
> >
>
> OK. I was not sure, as the code is older than that. But I guess the copyright
> goes by the file, not the code...
>
>
> >> + This file is part of GDB.
> >> + + This program is free software; you can redistribute it and/or
> >> modify
> >> + it under the terms of the GNU General Public License as published by
> >> + the Free Software Foundation; either version 2 of the License, or
> >> + (at your option) any later version.
> >> + + This program is distributed in the hope that it will be useful,
> >> + but WITHOUT ANY WARRANTY; without even the implied warranty of
> >> + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
> >> + GNU General Public License for more details.
> >> + + You should have received a copy of the GNU General Public License
> >> + along with this program; if not, write to the Free Software
> >> + Foundation, Inc., 59 Temple Place - Suite 330,
> >> + Boston, MA 02111-1307, USA. */
> >> + + extern void gdb_disassembly (char *file_string,
> >> + int line_num,
> >> + int mixed_source_and_assembly,
> >> + int how_many, CORE_ADDR low, CORE_ADDR high);
> >
> >
> > It needs #ifdef DISASM_H et.al.
>
> Yes, how could I forget!
>
> > It should take an explicit ui_out parameter.
> >
>
> Good point. Of all people I should have remembered that one ;-)
>
> > As for the rest vis:
> >
> >> ! static int
> >> ! gdb_dis_asm_read_memory (bfd_vma memaddr, bfd_byte * myaddr,
> >> ! unsigned int len, disassemble_info * info)
> >> ! {
> >> ! extern struct target_ops exec_ops;
> >
> >
> > I guess we all get to grit our teeth because we know you're just moving
> > around existing code :-)
> >
>
> It seems that it may need some clean-up. But you are right, I am just moving
> code and I like to do the least possible changes on that pass.
>
> One of us should take a look and see if there is something else. It will be
> easier to maintain it as it becomes the only disassembler code instead of one of
> many.
>
>
> Thanks for looking at this. I will make the changes and check it in.
>
> Regards,
> Fernando
>
>
> --
> Fernando Nasser
> Red Hat - Toronto E-Mail: fnasser@redhat.com
> 2323 Yonge Street, Suite #300
> Toronto, Ontario M4P 2C9
next prev parent reply other threads:[~2002-09-30 16:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-26 16:15 Fernando Nasser
2002-09-26 19:15 ` Andrew Cagney
2002-09-30 8:10 ` Fernando Nasser
2002-09-30 8:40 ` Andrew Cagney
2002-09-30 9:44 ` Elena Zannoni [this message]
2002-09-30 8:58 ` Fernando Nasser
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=15768.32428.867105.772361@localhost.redhat.com \
--to=ezannoni@redhat.com \
--cc=ac131313@redhat.com \
--cc=fnasser@redhat.com \
--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