gdb/29: gdb has fixed size MAX_SECTIONS

Michael Elizabeth Chastain chastain@cygnus.com
Mon Feb 19 09:48:00 GMT 2001


The following reply was made to PR gdb/29; it has been noted by GNATS.

From: Michael Elizabeth Chastain <chastain@cygnus.com>
To: gdb-gnats@sources.redhat.com
Cc:  
Subject: Re: gdb/29: gdb has fixed size MAX_SECTIONS
Date: Mon, 19 Feb 2001 09:43:16 -0800

 This happens when a Solaris program is built with SUNWspro cc version 4.2
 and the "-xF" flag is turned on.  From the man page:
 
      -xF  Enables performance analysis of the executable using
           the WorkShop Analyzer.  (See analyzer(1) man pages.)
 
           Produces code that can be reordered at the function
           level.  Each function in the file is placed in a
           separate section; for example, functions foo() and
           bar() will be placed in the sections .text%foo and
           .text%bar , respectively.  Function ordering in the
           executable can be controlled by using -xF in conjunc-
           tion with the -M option to ld (see ld(1)).
 
           This option also causes the assembler to generate some
           debugging information necessary for data collection in
           the object file.
 
 This flag was used to build the X11 libraries on Solaris
 (specifically, /usr/openwin/lib/libX11.a) so the problem happens on
 static-linked programs that use X11 on Solaris 2.6, even programs that
 were mostly compiled with gcc.



More information about the Gdb-prs mailing list