This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
gdb/29: gdb has fixed size MAX_SECTIONS
- To: gdb-gnats at sources dot redhat dot com
- Subject: gdb/29: gdb has fixed size MAX_SECTIONS
- From: chastain at redhat dot com
- Date: 19 Feb 2001 17:19:34 -0000
- Reply-To: chastain at redhat dot com
>Number: 29
>Category: gdb
>Synopsis: gdb has fixed size MAX_SECTIONS
>Confidential: no
>Severity: critical
>Priority: high
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Mon Feb 19 09:28:01 PST 2001
>Closed-Date:
>Last-Modified:
>Originator: chastain@redhat.com
>Release: gdb cvs 2001-02-18
>Organization:
>Environment:
Solaris 2.6
>Description:
gdb has fixed size MAX_SECTIONS of 64.
This fails on executables with more than 64 sections.
The ANOFFSET macro quietly accesses out-of-bounds memory.
I've seen such executables on Solaris 2.6 (gdb itself when linked with static X11 libraries),
but do not have a reproducable test case.
>How-To-Repeat:
>Fix:
MAX_SECTIONS must die.
Use dynamic arrays with sizes set by the bfd section count.
>Release-Note:
>Audit-Trail:
>Unformatted: