Why gdb fail to make

Why gdb fail to make

why gdb fail to configure & make. i have already configure and make binutils
and gcc an gcc-c++ for target i386-elf smoothly but  gdb-7.6.50-2i fail to
build i am using cygwin version 2.774 on window7. how can remove this
error:- 

Shine <at> Shine-PC /usr/src/gdb-elf-7.6.50-2
$ ../gdb-7.6.50-2/configure --prefix=/usr/local/i386 --target=i386-elf

Shine <at> Shine-PC /usr/src/gdb-elf-7.6.50-2

make[7]: Entering directory
`/usr/src/gdb-elf-7.6.50-2/gdb/build-gnulib/import'
make[8]: Entering directory
`/usr/src/gdb-elf-7.6.50-2/gdb/build-gnulib/import'
make[8]: Nothing to be done for `all-am'.
make[8]: Leaving directory
`/usr/src/gdb-elf-7.6.50-2/gdb/build-gnulib/import'
make[7]: Leaving directory
`/usr/src/gdb-elf-7.6.50-2/gdb/build-gnulib/import'
make[6]: Leaving directory
`/usr/src/gdb-elf-7.6.50-2/gdb/build-gnulib/import'
make[5]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/gdb/build-gnulib'
make[4]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/gdb/build-gnulib'
make[3]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/gdb'
gcc -g -O2    -I. -I../../gdb-7.6.50-2/gdb -I../../gdb-7.6.50-2/gdb/common
-I../../gdb-7.6.50-2/gdb/config 
-DLOCALEDIR="\"/usr/local/i386/share/locale\"" -DHAVE_CONFIG_H
-I../../gdb-7.6.50-2/gdb/../include/opcode
-I../../gdb-7.6.50-2/gdb/../opcodes/..
-I../../gdb-7.6.50-2/gdb/../readline/..  -I../bfd
-I../../gdb-7.6.50-2/gdb/../bfd -I../../gdb-7.6.50-2/gdb/../include
-I../libdecnumber -I../../gdb-7.6.50-2/gdb/../libdecnumber  
-I../../gdb-7.6.50-2/gdb/gnulib/import -Ibuild-gnulib/import   -DTUI=1 
-I/usr/include/python2.7 -I/usr/include/python2.7 -Wall
-Wdeclaration-after-statement -Wpointer-arith -Wformat-nonliteral
-Wno-unused -Wunused-value -Wunused-function -Wno-switch
-Wno-char-subscripts -Wmissing-prototypes -Wdeclaration-after-statement
-Werror -c -o gdb.o -MT gdb.o -MMD -MP  -MF .deps/gdb.Tpo
../../gdb-7.6.50-2/gdb/gdb.c
In file included from ../../gdb-7.6.50-2/gdb/defs.h:803,
                 from ../../gdb-7.6.50-2/gdb/gdb.c:19:
../../gdb-7.6.50-2/gdb/utils.h:283: warning: parameter has incomplete type
Makefile:979: recipe for target `gdb.o' failed
make[2]: *** [gdb.o] Error 1
make[2]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/gdb'
Makefile:8261: recipe for target `all-gdb' failed
make[1]: *** [all-gdb] Error 2
make[1]: Leaving directory `/usr/src/gdb-elf-7.6.50-2'
Makefile:831: recipe for target `all' failed
make: *** [all] Error 2

--

-- 
View this message in context: http://old.nabble.com/Why-gdb-fail-to-make-tp35401133p35401133.html
Sent from the Gnu - gdb - General mailing list archive at Nabble.com.

Why gdb fail to make

Why gdb fail to make

why gdb fail to configure & make. i have already configure and make binutils
and gcc an gcc-c++ for target i386-elf smoothly but  gdb-7.6.50-2i fail to
build i am using cygwin version 2.774 on window7. how can remove this
error:- 

Shine <at> Shine-PC /usr/src/gdb-elf-7.6.50-2
$ ../gdb-7.6.50-2/configure --prefix=/usr/local/i386 --target=i386-elf

Shine <at> Shine-PC /usr/src/gdb-elf-7.6.50-2
$ make
make[1]: Entering directory `/usr/src/gdb-elf-7.6.50-2'
make[2]: Entering directory `/usr/src/gdb-elf-7.6.50-2/libiberty'
make[3]: Entering directory `/usr/src/gdb-elf-7.6.50-2/libiberty/testsuite'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/libiberty/testsuite'
make[2]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/libiberty'
make[2]: Entering directory `/usr/src/gdb-elf-7.6.50-2/intl'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/intl'
make[2]: Entering directory `/usr/src/gdb-elf-7.6.50-2/bfd'
Making info in doc
make[3]: Entering directory `/usr/src/gdb-elf-7.6.50-2/bfd/doc'
make[3]: Nothing to be done for `info'.
make[3]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/bfd/doc'
Making info in po
make[3]: Entering directory `/usr/src/gdb-elf-7.6.50-2/bfd/po'
make[3]: Nothing to be done for `info'.
make[3]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/bfd/po'
make[3]: Entering directory `/usr/src/gdb-elf-7.6.50-2/bfd'
make[3]: Nothing to be done for `info-am'.
make[3]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/bfd'
make  all-recursive
make[3]: Entering directory `/usr/src/gdb-elf-7.6.50-2/bfd'
Making all in doc
make[4]: Entering directory `/usr/src/gdb-elf-7.6.50-2/bfd/doc'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/bfd/doc'
Making all in po
make[4]: Entering directory `/usr/src/gdb-elf-7.6.50-2/bfd/po'
file=`echo ../../../gdb-7.6.50-2/bfd/po/da | sed 's,.*/,,'`.gmo \
  && rm -f $file && PATH=../src:$PATH : -o $file
../../../gdb-7.6.50-2/bfd/po/da.po
file=`echo ../../../gdb-7.6.50-2/bfd/po/es | sed 's,.*/,,'`.gmo \
  && rm -f $file && PATH=../src:$PATH : -o $file
../../../gdb-7.6.50-2/bfd/po/es.po
file=`echo ../../../gdb-7.6.50-2/bfd/po/fr | sed 's,.*/,,'`.gmo \
  && rm -f $file && PATH=../src:$PATH : -o $file
../../../gdb-7.6.50-2/bfd/po/fr.po
file=`echo ../../../gdb-7.6.50-2/bfd/po/ja | sed 's,.*/,,'`.gmo \
  && rm -f $file && PATH=../src:$PATH : -o $file
../../../gdb-7.6.50-2/bfd/po/ja.po
file=`echo ../../../gdb-7.6.50-2/bfd/po/vi | sed 's,.*/,,'`.gmo \
  && rm -f $file && PATH=../src:$PATH : -o $file
../../../gdb-7.6.50-2/bfd/po/vi.po
file=`echo ../../../gdb-7.6.50-2/bfd/po/zh_CN | sed 's,.*/,,'`.gmo \
  && rm -f $file && PATH=../src:$PATH : -o $file
../../../gdb-7.6.50-2/bfd/po/zh_CN.po
file=`echo ../../../gdb-7.6.50-2/bfd/po/fi | sed 's,.*/,,'`.gmo \
  && rm -f $file && PATH=../src:$PATH : -o $file
../../../gdb-7.6.50-2/bfd/po/fi.po
file=`echo ../../../gdb-7.6.50-2/bfd/po/id | sed 's,.*/,,'`.gmo \
  && rm -f $file && PATH=../src:$PATH : -o $file
../../../gdb-7.6.50-2/bfd/po/id.po
file=`echo ../../../gdb-7.6.50-2/bfd/po/ru | sed 's,.*/,,'`.gmo \
  && rm -f $file && PATH=../src:$PATH : -o $file
../../../gdb-7.6.50-2/bfd/po/ru.po
file=`echo ../../../gdb-7.6.50-2/bfd/po/uk | sed 's,.*/,,'`.gmo \
  && rm -f $file && PATH=../src:$PATH : -o $file
../../../gdb-7.6.50-2/bfd/po/uk.po
make[4]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/bfd/po'
make[4]: Entering directory `/usr/src/gdb-elf-7.6.50-2/bfd'
make[4]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/bfd'
make[3]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/bfd'
make[2]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/bfd'
make[2]: Entering directory `/usr/src/gdb-elf-7.6.50-2/opcodes'
make  all-recursive
make[3]: Entering directory `/usr/src/gdb-elf-7.6.50-2/opcodes'
Making all in .
make[4]: Entering directory `/usr/src/gdb-elf-7.6.50-2/opcodes'
make[4]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/opcodes'
Making all in po
make[4]: Entering directory `/usr/src/gdb-elf-7.6.50-2/opcodes/po'
file=`echo ../../../gdb-7.6.50-2/opcodes/po/da | sed 's,.*/,,'`.gmo \
  && rm -f $file && PATH=../src:$PATH : -o $file
../../../gdb-7.6.50-2/opcodes/po/da.po
file=`echo ../../../gdb-7.6.50-2/opcodes/po/es | sed 's,.*/,,'`.gmo \
  && rm -f $file && PATH=../src:$PATH : -o $file
../../../gdb-7.6.50-2/opcodes/po/es.po
file=`echo ../../../gdb-7.6.50-2/opcodes/po/fi | sed 's,.*/,,'`.gmo \
  && rm -f $file && PATH=../src:$PATH : -o $file
../../../gdb-7.6.50-2/opcodes/po/fi.po
file=`echo ../../../gdb-7.6.50-2/opcodes/po/fr | sed 's,.*/,,'`.gmo \
  && rm -f $file && PATH=../src:$PATH : -o $file
../../../gdb-7.6.50-2/opcodes/po/fr.po
file=`echo ../../../gdb-7.6.50-2/opcodes/po/ga | sed 's,.*/,,'`.gmo \
  && rm -f $file && PATH=../src:$PATH : -o $file
../../../gdb-7.6.50-2/opcodes/po/ga.po
file=`echo ../../../gdb-7.6.50-2/opcodes/po/id | sed 's,.*/,,'`.gmo \
  && rm -f $file && PATH=../src:$PATH : -o $file
../../../gdb-7.6.50-2/opcodes/po/id.po
file=`echo ../../../gdb-7.6.50-2/opcodes/po/nl | sed 's,.*/,,'`.gmo \
  && rm -f $file && PATH=../src:$PATH : -o $file
../../../gdb-7.6.50-2/opcodes/po/nl.po
file=`echo ../../../gdb-7.6.50-2/opcodes/po/vi | sed 's,.*/,,'`.gmo \
  && rm -f $file && PATH=../src:$PATH : -o $file
../../../gdb-7.6.50-2/opcodes/po/vi.po
file=`echo ../../../gdb-7.6.50-2/opcodes/po/zh_CN | sed 's,.*/,,'`.gmo \
  && rm -f $file && PATH=../src:$PATH : -o $file
../../../gdb-7.6.50-2/opcodes/po/zh_CN.po
file=`echo ../../../gdb-7.6.50-2/opcodes/po/it | sed 's,.*/,,'`.gmo \
  && rm -f $file && PATH=../src:$PATH : -o $file
../../../gdb-7.6.50-2/opcodes/po/it.po
file=`echo ../../../gdb-7.6.50-2/opcodes/po/uk | sed 's,.*/,,'`.gmo \
  && rm -f $file && PATH=../src:$PATH : -o $file
../../../gdb-7.6.50-2/opcodes/po/uk.po
make[4]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/opcodes/po'
make[3]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/opcodes'
make[2]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/opcodes'
make[2]: Entering directory `/usr/src/gdb-elf-7.6.50-2/etc'
for f in standards.info configure.info; do \
  if test -f ../../gdb-7.6.50-2/etc/`echo $f | sed -e 's/.info$/.texi/'`;
then \
    if make "MAKEINFO=makeinfo --split-size=5000000 --split-size=5000000"
$f; then \
      true; \
    else \
      exit 1; \
    fi; \
  fi; \
done
make[3]: Entering directory `/usr/src/gdb-elf-7.6.50-2/etc'
make[3]: `standards.info' is up to date.
make[3]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/etc'
make[3]: Entering directory `/usr/src/gdb-elf-7.6.50-2/etc'
make[3]: `configure.info' is up to date.
make[3]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/etc'
make[2]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/etc'
make[2]: Entering directory `/usr/src/gdb-elf-7.6.50-2/libdecnumber'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/libdecnumber'
make[2]: Entering directory `/usr/src/gdb-elf-7.6.50-2/readline'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/readline'
make[2]: Entering directory `/usr/src/gdb-elf-7.6.50-2/gdb'
make[3]: Entering directory `/usr/src/gdb-elf-7.6.50-2/gdb'
make[4]: Entering directory `/usr/src/gdb-elf-7.6.50-2/gdb/build-gnulib'
make[5]: Entering directory `/usr/src/gdb-elf-7.6.50-2/gdb/build-gnulib'
make[6]: Entering directory
`/usr/src/gdb-elf-7.6.50-2/gdb/build-gnulib/import'
make  all-recursive
make[7]: Entering directory
`/usr/src/gdb-elf-7.6.50-2/gdb/build-gnulib/import'
make[8]: Entering directory
`/usr/src/gdb-elf-7.6.50-2/gdb/build-gnulib/import'
make[8]: Nothing to be done for `all-am'.
make[8]: Leaving directory
`/usr/src/gdb-elf-7.6.50-2/gdb/build-gnulib/import'
make[7]: Leaving directory
`/usr/src/gdb-elf-7.6.50-2/gdb/build-gnulib/import'
make[6]: Leaving directory
`/usr/src/gdb-elf-7.6.50-2/gdb/build-gnulib/import'
make[5]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/gdb/build-gnulib'
make[4]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/gdb/build-gnulib'
make[3]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/gdb'
gcc -g -O2    -I. -I../../gdb-7.6.50-2/gdb -I../../gdb-7.6.50-2/gdb/common
-I../../gdb-7.6.50-2/gdb/config 
-DLOCALEDIR="\"/usr/local/i386/share/locale\"" -DHAVE_CONFIG_H
-I../../gdb-7.6.50-2/gdb/../include/opcode
-I../../gdb-7.6.50-2/gdb/../opcodes/..
-I../../gdb-7.6.50-2/gdb/../readline/..  -I../bfd
-I../../gdb-7.6.50-2/gdb/../bfd -I../../gdb-7.6.50-2/gdb/../include
-I../libdecnumber -I../../gdb-7.6.50-2/gdb/../libdecnumber  
-I../../gdb-7.6.50-2/gdb/gnulib/import -Ibuild-gnulib/import   -DTUI=1 
-I/usr/include/python2.7 -I/usr/include/python2.7 -Wall
-Wdeclaration-after-statement -Wpointer-arith -Wformat-nonliteral
-Wno-unused -Wunused-value -Wunused-function -Wno-switch
-Wno-char-subscripts -Wmissing-prototypes -Wdeclaration-after-statement
-Werror -c -o gdb.o -MT gdb.o -MMD -MP  -MF .deps/gdb.Tpo
../../gdb-7.6.50-2/gdb/gdb.c
In file included from ../../gdb-7.6.50-2/gdb/defs.h:803,
                 from ../../gdb-7.6.50-2/gdb/gdb.c:19:
../../gdb-7.6.50-2/gdb/utils.h:283: warning: parameter has incomplete type
Makefile:979: recipe for target `gdb.o' failed
make[2]: *** [gdb.o] Error 1
make[2]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/gdb'
Makefile:8261: recipe for target `all-gdb' failed
make[1]: *** [all-gdb] Error 2
make[1]: Leaving directory `/usr/src/gdb-elf-7.6.50-2'
Makefile:831: recipe for target `all' failed
make: *** [all] Error 2

--

-- 
View this message in context: http://old.nabble.com/Why-gdb-fail-to-make-tp35401125p35401125.html
Sent from the Gnu - gdb - General mailing list archive at Nabble.com.

Why gdb fail to make

why gdb fail to configure & make. i have already configure and make binutils
and gcc an gcc-c++ for target i386-elf smoothly but  gdb-7.6.50-2i fail to
build i am using cygwin version 2.774 on window7. how can remove this
error:- 

Shine <at> Shine-PC /usr/src/gdb-elf-7.6.50-2
$ ../gdb-7.6.50-2/configure --prefix=/usr/local/i386 --target=i386-elf

Shine <at> Shine-PC /usr/src/gdb-elf-7.6.50-2
$ make
make[1]: Entering directory `/usr/src/gdb-elf-7.6.50-2'
make[2]: Entering directory `/usr/src/gdb-elf-7.6.50-2/libiberty'
make[3]: Entering directory `/usr/src/gdb-elf-7.6.50-2/libiberty/testsuite'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/libiberty/testsuite'
make[2]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/libiberty'
make[2]: Entering directory `/usr/src/gdb-elf-7.6.50-2/intl'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/intl'
make[2]: Entering directory `/usr/src/gdb-elf-7.6.50-2/bfd'
Making info in doc
make[3]: Entering directory `/usr/src/gdb-elf-7.6.50-2/bfd/doc'
make[3]: Nothing to be done for `info'.
make[3]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/bfd/doc'
Making info in po
make[3]: Entering directory `/usr/src/gdb-elf-7.6.50-2/bfd/po'
make[3]: Nothing to be done for `info'.
make[3]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/bfd/po'
make[3]: Entering directory `/usr/src/gdb-elf-7.6.50-2/bfd'
make[3]: Nothing to be done for `info-am'.
make[3]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/bfd'
make  all-recursive
make[3]: Entering directory `/usr/src/gdb-elf-7.6.50-2/bfd'
Making all in doc
make[4]: Entering directory `/usr/src/gdb-elf-7.6.50-2/bfd/doc'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/bfd/doc'
Making all in po
make[4]: Entering directory `/usr/src/gdb-elf-7.6.50-2/bfd/po'
file=`echo ../../../gdb-7.6.50-2/bfd/po/da | sed 's,.*/,,'`.gmo \
  && rm -f $file && PATH=../src:$PATH : -o $file
../../../gdb-7.6.50-2/bfd/po/da.po
file=`echo ../../../gdb-7.6.50-2/bfd/po/es | sed 's,.*/,,'`.gmo \
  && rm -f $file && PATH=../src:$PATH : -o $file
../../../gdb-7.6.50-2/bfd/po/es.po
file=`echo ../../../gdb-7.6.50-2/bfd/po/fr | sed 's,.*/,,'`.gmo \
  && rm -f $file && PATH=../src:$PATH : -o $file
../../../gdb-7.6.50-2/bfd/po/fr.po
file=`echo ../../../gdb-7.6.50-2/bfd/po/ja | sed 's,.*/,,'`.gmo \
  && rm -f $file && PATH=../src:$PATH : -o $file
../../../gdb-7.6.50-2/bfd/po/ja.po
file=`echo ../../../gdb-7.6.50-2/bfd/po/vi | sed 's,.*/,,'`.gmo \
  && rm -f $file && PATH=../src:$PATH : -o $file
../../../gdb-7.6.50-2/bfd/po/vi.po
file=`echo ../../../gdb-7.6.50-2/bfd/po/zh_CN | sed 's,.*/,,'`.gmo \
  && rm -f $file && PATH=../src:$PATH : -o $file
../../../gdb-7.6.50-2/bfd/po/zh_CN.po
file=`echo ../../../gdb-7.6.50-2/bfd/po/fi | sed 's,.*/,,'`.gmo \
  && rm -f $file && PATH=../src:$PATH : -o $file
../../../gdb-7.6.50-2/bfd/po/fi.po
file=`echo ../../../gdb-7.6.50-2/bfd/po/id | sed 's,.*/,,'`.gmo \
  && rm -f $file && PATH=../src:$PATH : -o $file
../../../gdb-7.6.50-2/bfd/po/id.po
file=`echo ../../../gdb-7.6.50-2/bfd/po/ru | sed 's,.*/,,'`.gmo \
  && rm -f $file && PATH=../src:$PATH : -o $file
../../../gdb-7.6.50-2/bfd/po/ru.po
file=`echo ../../../gdb-7.6.50-2/bfd/po/uk | sed 's,.*/,,'`.gmo \
  && rm -f $file && PATH=../src:$PATH : -o $file
../../../gdb-7.6.50-2/bfd/po/uk.po
make[4]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/bfd/po'
make[4]: Entering directory `/usr/src/gdb-elf-7.6.50-2/bfd'
make[4]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/bfd'
make[3]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/bfd'
make[2]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/bfd'
make[2]: Entering directory `/usr/src/gdb-elf-7.6.50-2/opcodes'
make  all-recursive
make[3]: Entering directory `/usr/src/gdb-elf-7.6.50-2/opcodes'
Making all in .
make[4]: Entering directory `/usr/src/gdb-elf-7.6.50-2/opcodes'
make[4]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/opcodes'
Making all in po
make[4]: Entering directory `/usr/src/gdb-elf-7.6.50-2/opcodes/po'
file=`echo ../../../gdb-7.6.50-2/opcodes/po/da | sed 's,.*/,,'`.gmo \
  && rm -f $file && PATH=../src:$PATH : -o $file
../../../gdb-7.6.50-2/opcodes/po/da.po
file=`echo ../../../gdb-7.6.50-2/opcodes/po/es | sed 's,.*/,,'`.gmo \
  && rm -f $file && PATH=../src:$PATH : -o $file
../../../gdb-7.6.50-2/opcodes/po/es.po
file=`echo ../../../gdb-7.6.50-2/opcodes/po/fi | sed 's,.*/,,'`.gmo \
  && rm -f $file && PATH=../src:$PATH : -o $file
../../../gdb-7.6.50-2/opcodes/po/fi.po
file=`echo ../../../gdb-7.6.50-2/opcodes/po/fr | sed 's,.*/,,'`.gmo \
  && rm -f $file && PATH=../src:$PATH : -o $file
../../../gdb-7.6.50-2/opcodes/po/fr.po
file=`echo ../../../gdb-7.6.50-2/opcodes/po/ga | sed 's,.*/,,'`.gmo \
  && rm -f $file && PATH=../src:$PATH : -o $file
../../../gdb-7.6.50-2/opcodes/po/ga.po
file=`echo ../../../gdb-7.6.50-2/opcodes/po/id | sed 's,.*/,,'`.gmo \
  && rm -f $file && PATH=../src:$PATH : -o $file
../../../gdb-7.6.50-2/opcodes/po/id.po
file=`echo ../../../gdb-7.6.50-2/opcodes/po/nl | sed 's,.*/,,'`.gmo \
  && rm -f $file && PATH=../src:$PATH : -o $file
../../../gdb-7.6.50-2/opcodes/po/nl.po
file=`echo ../../../gdb-7.6.50-2/opcodes/po/vi | sed 's,.*/,,'`.gmo \
  && rm -f $file && PATH=../src:$PATH : -o $file
../../../gdb-7.6.50-2/opcodes/po/vi.po
file=`echo ../../../gdb-7.6.50-2/opcodes/po/zh_CN | sed 's,.*/,,'`.gmo \
  && rm -f $file && PATH=../src:$PATH : -o $file
../../../gdb-7.6.50-2/opcodes/po/zh_CN.po
file=`echo ../../../gdb-7.6.50-2/opcodes/po/it | sed 's,.*/,,'`.gmo \
  && rm -f $file && PATH=../src:$PATH : -o $file
../../../gdb-7.6.50-2/opcodes/po/it.po
file=`echo ../../../gdb-7.6.50-2/opcodes/po/uk | sed 's,.*/,,'`.gmo \
  && rm -f $file && PATH=../src:$PATH : -o $file
../../../gdb-7.6.50-2/opcodes/po/uk.po
make[4]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/opcodes/po'
make[3]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/opcodes'
make[2]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/opcodes'
make[2]: Entering directory `/usr/src/gdb-elf-7.6.50-2/etc'
for f in standards.info configure.info; do \
  if test -f ../../gdb-7.6.50-2/etc/`echo $f | sed -e 's/.info$/.texi/'`;
then \
    if make "MAKEINFO=makeinfo --split-size=5000000 --split-size=5000000"
$f; then \
      true; \
    else \
      exit 1; \
    fi; \
  fi; \
done
make[3]: Entering directory `/usr/src/gdb-elf-7.6.50-2/etc'
make[3]: `standards.info' is up to date.
make[3]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/etc'
make[3]: Entering directory `/usr/src/gdb-elf-7.6.50-2/etc'
make[3]: `configure.info' is up to date.
make[3]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/etc'
make[2]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/etc'
make[2]: Entering directory `/usr/src/gdb-elf-7.6.50-2/libdecnumber'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/libdecnumber'
make[2]: Entering directory `/usr/src/gdb-elf-7.6.50-2/readline'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/readline'
make[2]: Entering directory `/usr/src/gdb-elf-7.6.50-2/gdb'
make[3]: Entering directory `/usr/src/gdb-elf-7.6.50-2/gdb'
make[4]: Entering directory `/usr/src/gdb-elf-7.6.50-2/gdb/build-gnulib'
make[5]: Entering directory `/usr/src/gdb-elf-7.6.50-2/gdb/build-gnulib'
make[6]: Entering directory
`/usr/src/gdb-elf-7.6.50-2/gdb/build-gnulib/import'
make  all-recursive
make[7]: Entering directory
`/usr/src/gdb-elf-7.6.50-2/gdb/build-gnulib/import'
make[8]: Entering directory
`/usr/src/gdb-elf-7.6.50-2/gdb/build-gnulib/import'
make[8]: Nothing to be done for `all-am'.
make[8]: Leaving directory
`/usr/src/gdb-elf-7.6.50-2/gdb/build-gnulib/import'
make[7]: Leaving directory
`/usr/src/gdb-elf-7.6.50-2/gdb/build-gnulib/import'
make[6]: Leaving directory
`/usr/src/gdb-elf-7.6.50-2/gdb/build-gnulib/import'
make[5]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/gdb/build-gnulib'
make[4]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/gdb/build-gnulib'
make[3]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/gdb'
gcc -g -O2    -I. -I../../gdb-7.6.50-2/gdb -I../../gdb-7.6.50-2/gdb/common
-I../../gdb-7.6.50-2/gdb/config 
-DLOCALEDIR="\"/usr/local/i386/share/locale\"" -DHAVE_CONFIG_H
-I../../gdb-7.6.50-2/gdb/../include/opcode
-I../../gdb-7.6.50-2/gdb/../opcodes/..
-I../../gdb-7.6.50-2/gdb/../readline/..  -I../bfd
-I../../gdb-7.6.50-2/gdb/../bfd -I../../gdb-7.6.50-2/gdb/../include
-I../libdecnumber -I../../gdb-7.6.50-2/gdb/../libdecnumber  
-I../../gdb-7.6.50-2/gdb/gnulib/import -Ibuild-gnulib/import   -DTUI=1 
-I/usr/include/python2.7 -I/usr/include/python2.7 -Wall
-Wdeclaration-after-statement -Wpointer-arith -Wformat-nonliteral
-Wno-unused -Wunused-value -Wunused-function -Wno-switch
-Wno-char-subscripts -Wmissing-prototypes -Wdeclaration-after-statement
-Werror -c -o gdb.o -MT gdb.o -MMD -MP  -MF .deps/gdb.Tpo
../../gdb-7.6.50-2/gdb/gdb.c
In file included from ../../gdb-7.6.50-2/gdb/defs.h:803,
                 from ../../gdb-7.6.50-2/gdb/gdb.c:19:
../../gdb-7.6.50-2/gdb/utils.h:283: warning: parameter has incomplete type
Makefile:979: recipe for target `gdb.o' failed
make[2]: *** [gdb.o] Error 1
make[2]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/gdb'
Makefile:8261: recipe for target `all-gdb' failed
make[1]: *** [all-gdb] Error 2
make[1]: Leaving directory `/usr/src/gdb-elf-7.6.50-2'
Makefile:831: recipe for target `all' failed
make: *** [all] Error 2

--

-- 
View this message in context: http://old.nabble.com/Why-gdb-fail-to-make-tp35401127p35401127.html
Sent from the Gnu - gdb - General mailing list archive at Nabble.com.

Why gdb fail to make

why gdb fail to configure & make. i have already configure and make binutils
and gcc an gcc-c++ for target i386-elf smoothly but  gdb-7.6.50-2i fail to
build i am using cygwin version 2.774 on window7. how can remove this
error:- 

Shine <at> Shine-PC /usr/src/gdb-elf-7.6.50-2
$ ../gdb-7.6.50-2/configure --prefix=/usr/local/i386 --target=i386-elf

Shine <at> Shine-PC /usr/src/gdb-elf-7.6.50-2

make[7]: Entering directory
`/usr/src/gdb-elf-7.6.50-2/gdb/build-gnulib/import'
make[8]: Entering directory
`/usr/src/gdb-elf-7.6.50-2/gdb/build-gnulib/import'
make[8]: Nothing to be done for `all-am'.
make[8]: Leaving directory
`/usr/src/gdb-elf-7.6.50-2/gdb/build-gnulib/import'
make[7]: Leaving directory
`/usr/src/gdb-elf-7.6.50-2/gdb/build-gnulib/import'
make[6]: Leaving directory
`/usr/src/gdb-elf-7.6.50-2/gdb/build-gnulib/import'
make[5]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/gdb/build-gnulib'
make[4]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/gdb/build-gnulib'
make[3]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/gdb'
gcc -g -O2    -I. -I../../gdb-7.6.50-2/gdb -I../../gdb-7.6.50-2/gdb/common
-I../../gdb-7.6.50-2/gdb/config 
-DLOCALEDIR="\"/usr/local/i386/share/locale\"" -DHAVE_CONFIG_H
-I../../gdb-7.6.50-2/gdb/../include/opcode
-I../../gdb-7.6.50-2/gdb/../opcodes/..
-I../../gdb-7.6.50-2/gdb/../readline/..  -I../bfd
-I../../gdb-7.6.50-2/gdb/../bfd -I../../gdb-7.6.50-2/gdb/../include
-I../libdecnumber -I../../gdb-7.6.50-2/gdb/../libdecnumber  
-I../../gdb-7.6.50-2/gdb/gnulib/import -Ibuild-gnulib/import   -DTUI=1 
-I/usr/include/python2.7 -I/usr/include/python2.7 -Wall
-Wdeclaration-after-statement -Wpointer-arith -Wformat-nonliteral
-Wno-unused -Wunused-value -Wunused-function -Wno-switch
-Wno-char-subscripts -Wmissing-prototypes -Wdeclaration-after-statement
-Werror -c -o gdb.o -MT gdb.o -MMD -MP  -MF .deps/gdb.Tpo
../../gdb-7.6.50-2/gdb/gdb.c
In file included from ../../gdb-7.6.50-2/gdb/defs.h:803,
                 from ../../gdb-7.6.50-2/gdb/gdb.c:19:
../../gdb-7.6.50-2/gdb/utils.h:283: warning: parameter has incomplete type
Makefile:979: recipe for target `gdb.o' failed
make[2]: *** [gdb.o] Error 1
make[2]: Leaving directory `/usr/src/gdb-elf-7.6.50-2/gdb'
Makefile:8261: recipe for target `all-gdb' failed
make[1]: *** [all-gdb] Error 2
make[1]: Leaving directory `/usr/src/gdb-elf-7.6.50-2'
Makefile:831: recipe for target `all' failed
make: *** [all] Error 2

--

-- 
View this message in context: http://old.nabble.com/Why-gdb-fail-to-make-tp35401135p35401135.html
Sent from the Gnu - gdb - General mailing list archive at Nabble.com.

RE: Issue using GDB for non-stop multi-core debugging.

Hi All,

Finally, I managed to fix my below issue with some code modifications in GDB.

I am herewith attaching the modified file(infrun_7.5.1_Patch.c) along with the original file(infrun_7.5.1.c).

It would be great if anyone could do a code review of my modifications and check if these modifications would
have some other adverse effects or if there is a better way to do what I have done now.

Regards,
Rejeesh

P.S: Let me know if I need to send this to any other mailing list to get this reviewed.

-----Original Message-----
From: Rejeesh S. Babu 
Sent: Thursday, February 14, 2013 11:28 AM
To: 'gdb <at> gnu.org'; 'gdb <at> sourceware.org'
Subject: RE: Issue using GDB for non-stop multi-core debugging.

Hi All,

Sorry that I need to keep asking this again as the below issue is seriously troubling me.

Would appreciate if anyone can patiently read my below query and help me out in any way....

For those who feel that the below mail is too long to read, I would re-word it in a single liner:

"GDB stepping fails in SMP multi-core system whenever core switching(0->1 OR 1->0) happens before
stepping is completed".

Right now, I am debugging GDB source code to see if I can fix it myself. Any hints (files to concentrate) in GDB
source code debugging is also appreciated.

Expecting prompt response.

Regards,
Rejeesh

-----Original Message-----
From: Rejeesh S. Babu
Sent: Tuesday, December 04, 2012 5:45 PM
To: 'gdb <at> gnu.org'; 'gdb <at> sourceware.org'
Subject: Issue using GDB for non-stop multi-core debugging.

Hi All,

We are using GDB 7.5 (via MI protocol) to debug a remote multi-core target in non-stop mode. We use custom GDB
Server and GDB thread packets are interpreted as hardware core for multi-core debugging.

Everything is working fine except that step over through a piece of code which is simultaneously accessed
by both cores is failing.

The failing scenario can be explained as below:

1. Core 0 is halted and core 1 is running before single stepping 2. When user single step core 0, GDB puts a BP in
next location and run the target 3. Since core 1 is also executing this piece of code, core 1 takes this BP
(GDB expect core 0 to take BP) 4. Our custom GDB Server sends the stop notification packet of core 1 5.
Irrespective of the fact that notification packet of core 1 was send, GDB tries to read register/memory
values of core0 (which is running) 6. GDB Server respond with error packet and GDB stops functioning

Packets exchanged between GDB and GDB Server for single step :

Sending packet: $m80009000,4#5e...Ack
Packet received: 0800e003
Sending packet: $m80009000,4#5e...Ack
Packet received: 0800e003
Sending packet: $qTStatus#49...Ack
Packet received: 
Sending packet: $m80009000,4#5e...Ack
Packet received: 0800e003
Sending packet: $m80009000,4#5e...Ack
Packet received: 0800e003
Sending packet: $Z0,8000b024,4#d6...Ack
Packet received: OK
Packet Z0 (software-breakpoint) is supported Sending packet: $vCont;c:1#13...Ack //GDB run core 1
Packet received: OK
  Notification received: Stop:T05thread:02; //Core 2 is halted stop notification captured Sending
packet: $vStopped#55...Ack Packet received: OK Sending packet: $Hg2#e1...Ack Packet received: OK
Sending packet: $g#67...Ack Packet received: 00000000008b0010e08f0080020000000800c7cf424cfb231a0000001a00000000000000000000001a000000000062cfb81962cfa412b97f00ca9a3b00004800020000006476bc800000bc80accdbb800000bc808722c73b4337c3336322cf1f00000000d0300577081fc7cf081fc7cf0000c7cf081fc7cf032387bd24b00080018b00107cf82198d64f000094c40e770000800024b00080
Sending packet: $Hg1#e0...Ack //Though Core 2 was halted, GDB is requesting for Core 1 details Packet
received: E 00 Sending packet: $g#67...Ack Packet received: 00000000008b0010e08f0080020000000800c7cf424cfb231a0000001a00000000000000000000001a000000000062cfb81962cfa412b97f00ca9a3b00004800020000006476bc800000bc80accdbb800000bc808722c73b4337c3336322cf1f00000000d0300577081fc7cf081fc7cf0000c7cf081fc7cf032387bd24b00080018b00107cf82198d64f000094c40e770000800024b00080
Target is executing.

Is there a way to overcome this limitation? Is there any commands in GDB to handle such scenarios? Or is there
any GDB patch? Or is it because something is missing in our custom GDB Server?

Any hint to help us progress is highly appreciated.

Thanking in anticipation,
Rejeesh
***** Confidentiality Statement/Disclaimer *****

This message and any attachments is intended for the sole use of the intended recipient. It may contain
confidential information. Any unauthorized use, dissemination or modification is strictly
prohibited. If you are not the intended recipient, please notify the sender immediately then delete it
from all your systems, and do not copy, use or print. Internet communications are not secure and it is the
responsibility of the recipient to make sure that it is virus/malicious code exempt.
The company/sender cannot be responsible for any unauthorized alterations or modifications made to the
contents. If you require any form of confirmation of the contents, please contact the company/sender.
The company/sender is not liable for any errors or omissions in the content of this message.

RE: Issue using GDB for non-stop multi-core debugging.

Hi All,

Sorry that I need to keep asking this again as the below issue is seriously troubling me.

Would appreciate if anyone can patiently read my below query and help me out in any way....

For those who feel that the below mail is too long to read, I would re-word it in a single liner:

"GDB stepping fails in SMP multi-core system whenever core switching(0->1 OR 1->0) happens before
stepping is completed".

Right now, I am debugging GDB source code to see if I can fix it myself. Any hints (files to concentrate) in GDB
source code debugging is also appreciated.

Expecting prompt response.

Regards,
Rejeesh

-----Original Message-----
From: Rejeesh S. Babu 
Sent: Tuesday, December 04, 2012 5:45 PM
To: 'gdb <at> gnu.org'; 'gdb <at> sourceware.org'
Subject: Issue using GDB for non-stop multi-core debugging.

Hi All,

We are using GDB 7.5 (via MI protocol) to debug a remote multi-core target in non-stop mode. We use custom GDB
Server and GDB thread packets are interpreted as hardware core for multi-core debugging.

Everything is working fine except that step over through a piece of code which is simultaneously accessed
by both cores is failing.

The failing scenario can be explained as below:

1. Core 0 is halted and core 1 is running before single stepping
2. When user single step core 0, GDB puts a BP in next location and run the target
3. Since core 1 is also executing this piece of code, core 1 takes this BP (GDB expect core 0 to take BP)
4. Our custom GDB Server sends the stop notification packet of core 1 
5. Irrespective of the fact that notification packet of core 1 was send, GDB tries to read register/memory
values of core0 (which is running)
6. GDB Server respond with error packet and GDB stops functioning

Packets exchanged between GDB and GDB Server for single step :

Sending packet: $m80009000,4#5e...Ack
Packet received: 0800e003
Sending packet: $m80009000,4#5e...Ack
Packet received: 0800e003
Sending packet: $qTStatus#49...Ack
Packet received: 
Sending packet: $m80009000,4#5e...Ack
Packet received: 0800e003
Sending packet: $m80009000,4#5e...Ack
Packet received: 0800e003
Sending packet: $Z0,8000b024,4#d6...Ack
Packet received: OK
Packet Z0 (software-breakpoint) is supported
Sending packet: $vCont;c:1#13...Ack //GDB run core 1
Packet received: OK
  Notification received: Stop:T05thread:02; //Core 2 is halted 
stop notification captured
Sending packet: $vStopped#55...Ack
Packet received: OK
Sending packet: $Hg2#e1...Ack
Packet received: OK
Sending packet: $g#67...Ack
Packet received: 00000000008b0010e08f0080020000000800c7cf424cfb231a0000001a00000000000000000000001a000000000062cfb81962cfa412b97f00ca9a3b00004800020000006476bc800000bc80accdbb800000bc808722c73b4337c3336322cf1f00000000d0300577081fc7cf081fc7cf0000c7cf081fc7cf032387bd24b00080018b00107cf82198d64f000094c40e770000800024b00080
Sending packet: $Hg1#e0...Ack //Though Core 2 was halted, GDB is requesting for Core 1 details
Packet received: E 00
Sending packet: $g#67...Ack
Packet received: 00000000008b0010e08f0080020000000800c7cf424cfb231a0000001a00000000000000000000001a000000000062cfb81962cfa412b97f00ca9a3b00004800020000006476bc800000bc80accdbb800000bc808722c73b4337c3336322cf1f00000000d0300577081fc7cf081fc7cf0000c7cf081fc7cf032387bd24b00080018b00107cf82198d64f000094c40e770000800024b00080
Target is executing.

Is there a way to overcome this limitation? Is there any commands in GDB to handle such scenarios? Or is there
any GDB patch? Or is it because something is missing in our custom GDB Server?

Any hint to help us progress is highly appreciated.

Thanking in anticipation,
Rejeesh
***** Confidentiality Statement/Disclaimer *****

This message and any attachments is intended for the sole use of the intended recipient. It may contain
confidential information. Any unauthorized use, dissemination or modification is strictly
prohibited. If you are not the intended recipient, please notify the sender immediately then delete it
from all your systems, and do not copy, use or print. Internet communications are not secure and it is the
responsibility of the recipient to make sure that it is virus/malicious code exempt.
The company/sender cannot be responsible for any unauthorized alterations or modifications made to the
contents. If you require any form of confirmation of the contents, please contact the company/sender.
The company/sender is not liable for any errors or omissions in the content of this message.

looking for a gdb-backend

Detect a C++ class writing in a memory location

I need to know if there is a way in gdb to detect if a function (any
function) of a specific C++ class (represented by a file myClass.cc) access
a specific memory location (let's say 0xffffbc). That will help me a lot.
Thanks.
--

-- 
View this message in context: http://old.nabble.com/Detect-a-C%2B%2B-class-writing-in-a-memory-location-tp34794154p34794154.html
Sent from the Gnu - gdb - General mailing list archive at Nabble.com.

Issue using GDB for non-stop multi-core debugging.

Hi All,

We are using GDB 7.5 (via MI protocol) to debug a remote multi-core target in non-stop mode. We use custom GDB
Server and GDB thread packets are interpreted as hardware core for multi-core debugging.

Everything is working fine except that step over through a piece of code which is simultaneously accessed
by both cores is failing.

The failing scenario can be explained as below:

1. Core 0 is halted and core 1 is running before single stepping
2. When user single step core 0, GDB puts a BP in next location and run the target
3. Since core 1 is also executing this piece of code, core 1 takes this BP (GDB expect core 0 to take BP)
4. Our custom GDB Server sends the stop notification packet of core 1 
5. Irrespective of the fact that notification packet of core 1 was send, GDB tries to read register/memory
values of core0 (which is running)
6. GDB Server respond with error packet and GDB stops functioning

Packets exchanged between GDB and GDB Server for single step :

Sending packet: $m80009000,4#5e...Ack
Packet received: 0800e003
Sending packet: $m80009000,4#5e...Ack
Packet received: 0800e003
Sending packet: $qTStatus#49...Ack
Packet received: 
Sending packet: $m80009000,4#5e...Ack
Packet received: 0800e003
Sending packet: $m80009000,4#5e...Ack
Packet received: 0800e003
Sending packet: $Z0,8000b024,4#d6...Ack
Packet received: OK
Packet Z0 (software-breakpoint) is supported
Sending packet: $vCont;c:1#13...Ack //GDB run core 1
Packet received: OK
  Notification received: Stop:T05thread:02; //Core 2 is halted 
stop notification captured
Sending packet: $vStopped#55...Ack
Packet received: OK
Sending packet: $Hg2#e1...Ack
Packet received: OK
Sending packet: $g#67...Ack
Packet received: 00000000008b0010e08f0080020000000800c7cf424cfb231a0000001a00000000000000000000001a000000000062cfb81962cfa412b97f00ca9a3b00004800020000006476bc800000bc80accdbb800000bc808722c73b4337c3336322cf1f00000000d0300577081fc7cf081fc7cf0000c7cf081fc7cf032387bd24b00080018b00107cf82198d64f000094c40e770000800024b00080
Sending packet: $Hg1#e0...Ack //Though Core 2 was halted, GDB is requesting for Core 1 details
Packet received: E 00
Sending packet: $g#67...Ack
Packet received: 00000000008b0010e08f0080020000000800c7cf424cfb231a0000001a00000000000000000000001a000000000062cfb81962cfa412b97f00ca9a3b00004800020000006476bc800000bc80accdbb800000bc808722c73b4337c3336322cf1f00000000d0300577081fc7cf081fc7cf0000c7cf081fc7cf032387bd24b00080018b00107cf82198d64f000094c40e770000800024b00080
Target is executing.

Is there a way to overcome this limitation? Is there any commands in GDB to handle such scenarios? Or is there
any GDB patch? Or is it because something is missing in our custom GDB Server?

Any hint to help us progress is highly appreciated.

Thanking in anticipation,
Rejeesh
***** Confidentiality Statement/Disclaimer *****

This message and any attachments is intended for the sole use of the intended recipient. It may contain
confidential information. Any unauthorized use, dissemination or modification is strictly
prohibited. If you are not the intended recipient, please notify the sender immediately then delete it
from all your systems, and do not copy, use or print. Internet communications are not secure and it is the
responsibility of the recipient to make sure that it is virus/malicious code exempt.
The company/sender cannot be responsible for any unauthorized alterations or modifications made to the
contents. If you require any form of confirmation of the contents, please contact the company/sender.
The company/sender is not liable for any errors or omissions in the content of this message.