Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>,
	       GDB Patches <gdb-patches@sourceware.org>
Cc: Gabriel Krisman Bertazi <gabriel@krisman.be>
Subject: Re: [PATCH 1/3] Making syscall information be per-arch, instead of global
Date: Fri, 14 Nov 2014 15:53:00 -0000	[thread overview]
Message-ID: <54662556.1090501@redhat.com> (raw)
In-Reply-To: <1415837887-28888-2-git-send-email-sergiodj@redhat.com>

On 11/13/2014 12:18 AM, Sergio Durigan Junior wrote:

> 	(xml_init_syscalls_info): Likewise.

Should mention the dropped const.

>  xml_init_syscalls_info (const char *filename)
>  {
>    char *full_file;
>    char *dirname;
> -  struct syscalls_info *sysinfo;
> +  struct syscalls_info *syscalls_info;
>    struct cleanup *back_to;
>  
>    full_file = xml_fetch_content_from_file (filename, gdb_datadir);
> @@ -266,41 +265,47 @@ xml_init_syscalls_info (const char *filename)
>    if (dirname != NULL)
>      make_cleanup (xfree, dirname);
>  
> -  sysinfo = syscall_parse_xml (full_file,
> +  syscalls_info = syscall_parse_xml (full_file,
>  			       xml_fetch_content_from_file, dirname);

The line after needs a reindent.

>    do_cleanups (back_to);
>  
> -  return sysinfo;
> +  return syscalls_info;
>  }
>  

> -  have_initialized_sysinfo = 1;
> +  /* If there was some error reading the XML file, we initialize
> +     gdbarch->syscalls_info anyway, in order to store information
> +     about our attempt.  */
> +  if (syscalls_info == NULL)
> +      syscalls_info = allocate_syscalls_info ();

Indentation here looks odd.

>
> -  if (sysinfo == NULL)
> +  if (syscalls_info->syscalls == NULL)
>      {

Otherwise looks good.

Thanks for doing this.

Thanks,
Pedro Alves


  reply	other threads:[~2014-11-14 15:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-13  0:18 [PATCH] Partial fix for PR breakpoints/10737: Make syscall info be per-arch " Sergio Durigan Junior
2014-11-13  0:18 ` [PATCH 2/3] Adjust calls for setting "catch syscall" information Sergio Durigan Junior
2014-11-14 15:53   ` Pedro Alves
2014-11-14 23:18     ` Sergio Durigan Junior
2014-11-13  0:18 ` [PATCH 3/3] Testcase Sergio Durigan Junior
2014-11-14 15:54   ` Pedro Alves
2014-11-18  3:30     ` Sergio Durigan Junior
2014-11-18 15:13       ` Pedro Alves
2014-11-18 20:20         ` Sergio Durigan Junior
2014-11-19  9:23           ` PowerPC: "set architecture" -> "Architecture not recognized" ? (was: Re: [PATCH 3/3] Testcase) Pedro Alves
2014-11-19 18:46             ` PowerPC: "set architecture" -> "Architecture not recognized" ? Sergio Durigan Junior
2014-11-20 10:48               ` Pedro Alves
2014-11-20 17:20                 ` Sergio Durigan Junior
2014-11-13  0:18 ` [PATCH 1/3] Making syscall information be per-arch, instead of global Sergio Durigan Junior
2014-11-14 15:53   ` Pedro Alves [this message]
2014-11-14 23:17     ` Sergio Durigan Junior
2014-11-20 17:34 ` [PATCH] Partial fix for PR breakpoints/10737: Make syscall info be per-arch " Sergio Durigan Junior

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=54662556.1090501@redhat.com \
    --to=palves@redhat.com \
    --cc=gabriel@krisman.be \
    --cc=gdb-patches@sourceware.org \
    --cc=sergiodj@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