[Bug gdb/14963] segfault on startup

["adrian.cheater at gmail dot com" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=14963

Adrian Cheater <adrian.cheater at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |adrian.cheater at gmail dot com

--- Comment #25 from Adrian Cheater <adrian.cheater at gmail dot com> ---
Created attachment 7573
  --> https://sourceware.org/bugzilla/attachment.cgi?id=7573&action=edit
3 failed strings from test-demangle when gdb 7.7 was configured with
CFLAGS='-DCP_DEMANGLE_DEBUG -ggdb3 -O0'

The pattern I'm seeing is when the parser hits the "reference->template
parameter 0" sections of the tree. It's grabbing a reference point of which it
is a subnode. Causing the parser to cycle back and recurse until it runs out of
stack or heap.

I'm still trying to get my head around this, having only started looking into
it about 2 days ago, but I have the following hypothesies.

- It's adding a reference to the near root of the tree when it shouldn't be
(which ends up as reference 0)
- The 'template parameter 0's might need to be 'template parameter 1's.
- References are allowed to be recursive, and at the time it fetches 'template
parameter 0', it's not grabbing the correct level.

Hoping someone with more experience can help me narrow it down, otherwise I'm
going to keep investigating. This bug is blocking a hobby project of mine, so
it's either fix this or shelve the project until someone else fixes it.

At any rate, the problem is likely to be somewhere in the get/set symbol
references but I don't know what the 'correct' behaviour is supposed to be. Is
this defined in a spec, or just a undefined detail?

-- 
You are receiving this mail because:
You are on the CC list for the bug.