[Bug fortran/11354] error in evaluating variable length fortranstrings causes stalls

["stephan.kramer at imperial dot ac.uk"<sourceware-bugzilla at sourceware dot org>]

http://sourceware.org/bugzilla/show_bug.cgi?id=11354

--- Comment #3 from Stephan Kramer <stephan.kramer at imperial dot ac.uk> 2011-04-29 16:26:39 UTC ---
Thanks for your response. I know proper modern fortran support is a more
longterm issue - really appreciate the effort that needs to go into that.
Hitting ctrl-c doesn't solve the issue as that breaks off printing the frame
info before even printing the line number, which rather limits the
functionality of gdb: no backtraces, no line numbers when stepping through the
code.

When you say I don't see this issue with fsf gdb, do you mean it doesn't stall?
Or, do you not see "Cannot access memory at address <random-address>". It's the
latter that is the real issue, because that causes the stalls in executables
with a large memory layout (not the example program of course); basically goes
through the lot of it before giving up. I still see this behaviour with gdb
version 7.2 on Ubuntu Natty.

Once again, the issue is not the faulty printing. We know we can work around
this with some pointer voodoo, it's the stalling that's causing us some real
headaches trying to debug things on a large executable.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.