This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
pending/1247: Re: cp-support.c:332: internal-error: cp_entire_prefix_len
- From: David Carlton <carlton at math dot stanford dot edu>
- To: Stephane dot Carrez at nerim dot fr
- Cc: gdb-gnats at sources dot redhat dot com
- Date: 20 Jun 2003 11:34:18 -0700
- Subject: pending/1247: Re: cp-support.c:332: internal-error: cp_entire_prefix_len
- References: <20030618205647.7913.qmail@sources.redhat.com>
>Number: 1247
>Category: pending
>Synopsis: Re: cp-support.c:332: internal-error: cp_entire_prefix_len
>Confidential: yes
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: change-request
>Submitter-Id: unknown
>Arrival-Date: Fri Jun 20 18:38:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:
>Release:
>Organization:
>Environment:
>Description:
On 18 Jun 2003 20:56:47 -0000, Stephane.Carrez@nerim.fr said:
> the problem is due to the fact that the operator function
> is '<' and not '<<'. The second '<' is the beginning of
> a template instantiation. This is wierd because you have
> no way (to my knowledge) to distinguish between:
> operator < <template instance>
> operator <<
> Since the second < is eat by the operator processing, we come up
> with a wrong result. Ideally, the demangler should insert a space
> after the operator <
Yes, I agree.
We should also consider turning this into a complaint (with a suitable
fallback return value, presumably the length of the entire string)
instead of an assertion: this is the second time we've been bitten by
this assertion failure. I'll work on this next week.
David Carlton
carlton@math.stanford.edu
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: