mirror of
https://github.com/bminor/binutils-gdb.git
synced 2026-02-06 15:01:30 +00:00
6150c6c061
The existing frecnt-2.c testcase reads the SFrame section from the provided DATA2 buffer. It exercises the sframe_decode (), sframe_decoder_get_num_fidx (), and sframe_decoder_get_funcdesc_v2 () APIs. Currently DATA2 file is the SFrame section created from the test input (mentioned in the comments in the file) in SFrame version 2 format. Moving forward, creating SFrame V2 section via GNU assembler and GNU ld will not be supported. But textual dump of SFrame V2 sections via readelf/objdump will need to be supported. Add a test similar to frecnt-2.c using SFrame version 2 binary data to the libsframe testsuite. Such a test will help ensure that sframe_decode () and related APIs remain tested for multiple supported arches till the support for dumping V2 sections is to be maintained. Duplicate frecnt-2.c to create a frecnt-v2.c, the latter will test with a SFrame V2 input section always. Reviewed-by: Jens Remus <jremus@linux.ibm.com> libsframe/ * Makefile.in: Regenerated. libsframe/testsuite/ * libsframe.decode/decode.exp: Add new test. * libsframe.decode/local.mk: Likewise * libsframe.decode/DATA-V2: New SFrame V2 test data file. * libsframe.decode/frecnt-v2.c: New test.
README for GNU development tools This directory contains various GNU compilers, assemblers, linkers, debuggers, etc., plus their support routines, definitions, and documentation. If you are receiving this as part of a GDB release, see the file gdb/README. If with a binutils release, see binutils/README, and so on. That'll give you info about this package -- supported targets, how to use it, how to report bugs, etc. It is now possible to automatically configure and build a variety of tools with one command. To build all of the tools contained herein, run the ``configure'' script here, e.g.: ./configure make To install them (by default in /usr/local/bin, /usr/local/lib, etc), then do: make install (If the configure script can't determine your type of computer, give it the name as an argument, for instance ``./configure sun4''. You can use the script ``config.sub'' to test whether a name is recognized; if it is, config.sub translates it to a triplet specifying CPU, vendor, and OS.) If you have more than one compiler on your system, it is often best to explicitly set CC in the environment before running configure, and to also set CC when running make. For example (assuming sh/bash/ksh): CC=gcc ./configure make A similar example using csh: setenv CC gcc ./configure make Much of the code and documentation enclosed is copyright by the Free Software Foundation, Inc. See the file COPYING or COPYING.LIB in the various directories, for a description of the GNU General Public License terms under which you can copy the files. REPORTING BUGS: Again, see gdb/README, binutils/README, etc., for info on where and how to report problems.