Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Hui Zhu <teawater@gmail.com>
To: "Sérgio Durigan Júnior" <sergiodj@linux.vnet.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/3] catch syscall -- try 5 -- Introduction
Date: Thu, 23 Apr 2009 15:28:00 -0000	[thread overview]
Message-ID: <daef60380904230827q116238a4w65f584aa94c6f7b@mail.gmail.com> (raw)
In-Reply-To: <1240499783.2000.92.camel@miki>

I got it because:
#ifndef HAVE_LIBEXPAT

/* Dummy functions to indicate that there's no support for fetching
   syscalls information.  */

static void
syscall_warn_user (void)
{
  static int have_warned = 0;
  if (!have_warned)
    {
      have_warned = 1;
      warning (_("Can not parse XML syscalls information; XML support was "
		 "disabled at compile time."));
    }
}

const struct syscalls_info *
xml_init_syscalls_info (const char *filename)
{
  syscall_warn_user ();
  return NULL;
}

int
xml_get_syscall_number (const struct syscalls_info *sysinfo,
                        const char *syscall_name)
{
  syscall_warn_user ();
  return UNKNOWN_SYSCALL;
}

const char *
xml_get_syscall_name (const struct syscalls_info *sysinfo,
                      int syscall_number)
{
  syscall_warn_user ();
  return NULL;
}

int
xml_number_of_syscalls (const struct syscalls_info *sysinfo)
{
  syscall_warn_user ();
  return 0;
}

const char **
xml_list_of_syscalls (const struct syscalls_info *sysinfo)
{
  syscall_warn_user ();
  return NULL;
}

#else /* ! HAVE_LIBEXPAT */

That is why I got this error.  I don't have LIBEXPAT.  Are you sure I
got a error is a right way?


Thanks,
Hui




2009/4/23 Sérgio Durigan Júnior <sergiodj@linux.vnet.ibm.com>:
> Hi Hui,
>
> On Thu, 2009-04-23 at 19:49 +0800, Hui Zhu wrote:
>> I got:
>
> You must apply all the 3 patches in order to compile and use the
> feature.
>
> Thanks,
>
> --
> Sérgio Durigan Júnior
> Linux on Power Toolchain - Software Engineer
> Linux Technology Center - LTC
> IBM Brazil
>
>


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

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-23  0:33 Sérgio Durigan Júnior
2009-04-23  1:18 ` Tom Tromey
2009-04-23  2:29   ` Sérgio Durigan Júnior
2009-04-23 18:23     ` Tom Tromey
2009-04-23 21:27       ` Tom Tromey
2009-04-24 13:47         ` Eli Zaretskii
2009-04-23 11:49 ` Hui Zhu
2009-04-23 15:16   ` Sérgio Durigan Júnior
2009-04-23 15:28     ` Hui Zhu [this message]
2009-04-23 15:52       ` Sérgio Durigan Júnior
2009-05-07  3:22 ` Hui Zhu
2009-05-08  1:23   ` Sérgio Durigan Júnior
2009-05-29 20:34     ` Sérgio Durigan Júnior
2009-06-29  2:15       ` Hui Zhu
2009-06-29 15:30         ` Tom Tromey
2009-05-17 20:43 ` Sérgio Durigan Júnior

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=daef60380904230827q116238a4w65f584aa94c6f7b@mail.gmail.com \
    --to=teawater@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=sergiodj@linux.vnet.ibm.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