Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Sérgio Durigan Júnior" <sergiodj@linux.vnet.ibm.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Pedro Alves <pedro@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 1/4] catch syscall -- try 4 -- Architecture-independent 	part
Date: Wed, 15 Apr 2009 23:12:00 -0000	[thread overview]
Message-ID: <1239837130.6345.21.camel@miki> (raw)
In-Reply-To: <20090331154452.GA13260@caradoc.them.org>

Hi Daniel,

I forgot to ask one more thing. Here it goes.

On Tue, 2009-03-31 at 11:44 -0400, Daniel Jacobowitz wrote:
> > With this you mean that I should remove the methods from gdbarch?
> 
> Yes, that's what I mean.
> 
> The way I think about this is that every gdbarch routine is a way for
> some architecture to handle things differently.  If we can make every
> architecture work the same way, we should do that instead.

Right, I'm already removing the code from gdbarch, but I'm facing a
problem that I'm unable to solve. Basically, I have a method in gdbarch
called gdbarch_xml_syscall_filename, which returns the name of the XML
that is going to be used. I need this because the XML file is different
for each supported arch.

The thing is that if I remove this, I can't think in a good way to
retrieve this filename. Is it ok to keep this single method inside
gdbarch?

Thanks,

-- 
Sérgio Durigan Júnior
Linux on Power Toolchain - Software Engineer
Linux Technology Center - LTC
IBM Brazil


      parent reply	other threads:[~2009-04-15 23:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-26  0:31 Sérgio Durigan Júnior
2009-01-26  0:51 ` Pedro Alves
2009-01-26  4:56   ` Sérgio Durigan Júnior
2009-01-26 17:04     ` Sérgio Durigan Júnior
2009-02-01 19:33       ` Daniel Jacobowitz
2009-02-25 21:44         ` Sérgio Durigan Júnior
2009-02-28  0:44           ` Daniel Jacobowitz
2009-03-08 18:16             ` Sérgio Durigan Júnior
2009-03-09 13:19               ` Daniel Jacobowitz
2009-03-09 14:09                 ` Sérgio Durigan Júnior
2009-03-09 18:39                   ` Pedro Alves
2009-03-09 18:56                     ` Daniel Jacobowitz
2009-03-09 18:31                 ` Pedro Alves
2009-03-29 21:16             ` Sérgio Durigan Júnior
2009-03-31 16:39               ` Daniel Jacobowitz
2009-04-09 19:29                 ` Sérgio Durigan Júnior
2009-04-09 19:36                   ` Daniel Jacobowitz
2009-04-09 20:21                     ` Sérgio Durigan Júnior
2009-04-15 23:12                 ` Sérgio Durigan Júnior [this message]

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=1239837130.6345.21.camel@miki \
    --to=sergiodj@linux.vnet.ibm.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.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