Hi,

    I'm seeing a bug with gdb 5.0 under Linux with scope and
exceptions.  If a variable is declared in a try block following a catch
(ret), the locals in the previous catch are not within scope.

    Does anyone have a fix for this?  The problem seems to exist in 4.18
as well.

int main()
{
    int a = 0;

    try {
        throw 42;
    } catch(int x) {
        a = x;          // gdb says 'No symbol "x" in current context.
    }

    try {
        int ret = 0;    // existance of this causes 'x' to be out of
scope above
    } catch(int) {
    }

    return 0;
}

Thanks,
Mike Morgan



_______________________________________________
Bug-gdb mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-gdb

Reply via email to