This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
Re: exp/1973: Crash when excess initializers for class arespecified
- From: Ramana Radhakrishnan <ramana dot radhakrishnan at codito dot com>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 3 Nov 2005 20:08:02 -0000
- Subject: Re: exp/1973: Crash when excess initializers for class arespecified
- Reply-to: Ramana Radhakrishnan <ramana dot radhakrishnan at codito dot com>
The following reply was made to PR exp/1973; it has been noted by GNATS.
From: Ramana Radhakrishnan <ramana.radhakrishnan@codito.com>
To: gdb-prs@sources.redhat.com, ghost@cs.msu.su, nobody@sources.redhat.com,
gdb-gnats@sources.redhat.com
Cc:
Subject: Re: exp/1973: Crash when excess initializers for class are
specified
Date: Fri, 04 Nov 2005 01:17:56 +0530
http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gdb&pr=1973
No longer segfaults . It behaves like this.
(gdb) set var b={1,2,3}
Cannot access memory at address 0x80495c4
With an equivalent C program the output from gdb is
(gdb) set var b={1,2,3}
too many initializers
This was with gdb GNU gdb 6.3.90-20051103-cvs on the 6.4 release branch.
cheers
Ramana
--
Ramana Radhakrishnan
GNU Tools
codito ergo sum (www.codito.com)