Displaying 9 results from an estimated 9 matches for "read_symbol".
Did you mean:
bad_symbol
2009 Jul 13
0
[PATCH, v2] x86-64: reduce symbol table size
...#define __OS "q" /* Operation Suffix */
#define __OP "r" /* Operand Prefix */
--- 2009-07-10.orig/xen/tools/symbols.c 2009-07-13 13:56:07.000000000 +0200
+++ 2009-07-10/xen/tools/symbols.c 2009-07-01 09:53:36.000000000 +0200
@@ -108,10 +108,7 @@ static int read_symbol(FILE *in, struct
else if (toupper((uint8_t)stype) == ''A'')
{
/* Keep these useful absolute symbols */
- if (strcmp(sym, "__kernel_syscall_via_break") &&
- strcmp(sym, "__kernel_syscall_via_epc") &&
- strcmp(sym, "__kernel_...
2007 Jul 23
0
make world error: symbols.c:123: warning: ignoring return value of ''fgets''
...------------------------------
make[5]: Entering directory `/home/admin/sources/xen-3.1.0-src/xen/tools''
gcc -Wall -Werror -Wstrict-prototypes -O2 -fomit-frame-pointer
-Wdeclaration-after-statement -o symbols symbols.c
cc1: warnings being treated as errors
symbols.c: In function ''read_symbol'':
symbols.c:83: warning: ignoring return value of ''fgets'', declared with
attribute warn_unused_result
make[5]: *** [symbols] Error 1
make[5]: Leaving directory `/home/admin/sources/xen-3.1.0-src/xen/tools''
make[4]: *** [default] Error 2
make[4]: Leaving director...
2008 Nov 17
0
Xen 3.3 compile error
.../tools/figlet''
make symbols
make[4]: Entering directory `/root/xen-3.3.0/xen/tools''
gcc -Wall -Werror -Wstrict-prototypes -O2 -fomit-frame-pointer
-fno-strict-aliasing -Wdeclaration-after-statement -o symbols symbols.c
cc1: warnings being treated as errors
symbols.c: In function ‘read_symbol’:
symbols.c:84: error: ignoring return value of ‘fgets’, declared with
attribute warn_unused_result
make[4]: *** [symbols] Error 1
make[4]: Leaving directory `/root/xen-3.3.0/xen/tools''
make[3]: *** [default] Error 2
make[3]: Leaving directory `/root/xen-3.3.0/xen/tools''
make[2]:...
2016 Apr 04
0
[PATCH 2/2] Use 'error' function for fprintf followed by exit.
.../tests/c-api/test-dlopen.c
@@ -24,6 +24,8 @@
#include <stdlib.h>
#include <unistd.h>
#include <dlfcn.h>
+#include <errno.h>
+#include <error.h>
/* We don't need the <guestfs.h> header file here. */
typedef struct guestfs_h guestfs_h;
@@ -44,10 +46,9 @@ read_symbol (void *lib, const char *symbol)
dlerror (); /* Clear error indicator. */
symval = dlsym (lib, symbol);
- if ((err = dlerror ()) != NULL) {
- fprintf (stderr, "could not read symbol: %s: %s\n", symbol, err);
- exit (EXIT_FAILURE);
- }
+ if ((err = dlerror ()) != NULL)
+...
2015 Aug 06
0
[PATCH v4 02/17] tests/c-api: Convert the C API tests to use the test harness.
...ef struct guestfs_h guestfs_h;
@@ -32,10 +37,6 @@ typedef guestfs_h *(*guestfs_create_t) (void);
typedef const char * (*guestfs_get_program_t) (guestfs_h *);
typedef void (*guestfs_close_t) (guestfs_h *);
-#ifndef LIBRARY
-#error "-DLIBRARY was not defined"
-#endif
-
static void *
read_symbol (void *lib, const char *symbol)
{
@@ -60,12 +61,6 @@ main (int argc, char *argv[])
guestfs_close_t guestfs_close;
guestfs_h *g;
- if (access (LIBRARY, X_OK) == -1) {
- fprintf (stderr, "test skipped because %s cannot be accessed: %m\n",
- LIBRARY);
- exit (77);...
2016 Apr 04
2
[PATCH 1/2] Use 'error' function consistently throughout.
Wherever we had code which did:
if (something_bad) {
perror (...);
exit (EXIT_FAILURE);
}
replace this with use of the error(3) function:
if (something_bad)
error (EXIT_FAILURE, errno, ...);
The error(3) function is supplied by glibc, or by gnulib on platforms
which don't have it, and is much more flexible than perror(3). Since
we already use error(3), there seems to be
2015 Aug 06
20
[PATCH v4 00/17] tests: Introduce test harness for running tests.
Since v3:
- A large number of fixes, especially for running the tests on
installed libguestfs.
- Fixed EXTRA_DIST rules throughout.
- Extra patch 17/17 which is a tidy-up of the generated XML
listing guests.
Rich.
2015 Jul 31
14
[PATCH v2 00/14] tests: Introduce test harness for running tests.
This is a more complete patch to add the test harness.
The only parts missing now are the language bindings (except OCaml).
The language bindings need a bit more thought. At the moment most
language binding tests are done through some sort of shell script like
perl/run-perl-tests which either runs each test itself or uses some
language-specific machinary to run each test. The problem with that
2015 Aug 04
16
[PATCH v3 01/16] tests: Introduce test harness for running tests.
Since v2:
- Add perl tests.
- Reworked and fixed the tests for virt-builder.
- Some further minor bug fixes.