Re: threads/2395: "info stack" works, but "stack-info-depth" fails

[Daniel Jacobowitz <drow@false.org>]

The following reply was made to PR threads/2395; it has been noted by GNATS.

From: Daniel Jacobowitz <drow@false.org>
To: oyvind.harboe@zylin.com
Cc: gdb-gnats@sources.redhat.com
Subject: Re: threads/2395: "info stack" works, but "stack-info-depth" fails
Date: Mon, 31 Dec 2007 09:44:10 -0500

 On Mon, Dec 31, 2007 at 11:23:41AM -0000, oyvind.harboe@zylin.com wrote:
 > This is better but not fixed in CVS HEAD.
 > 
 > See this bug report for details:
 > 
 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=86676
 
 790-stack-info-depth
 &"Cannot access memory at address 0xdeadbeeb\n"
 790^error,msg="Cannot access memory at address 0xdeadbeeb"
 791-stack-info-depth
 Cannot access memory at address 0xdeadbeeb
 (gdb) 
 Cannot access memory at address 0xdeadbeeb
 &"Cannot access memory at address 0xdeadbeeb\n"
 791^error,msg="Cannot access memory at address 0xdeadbeeb"
 (gdb) 
 info stack
 792-interpreter-exec console "info stack"
 ~"#0  0x00000018 in ?? ()\n"
 #0  0x00000018 in ?? ()
 ~"#1  0x000088d0 in Cyg_Thread::exit () at
 /ecos-c/cygwin/tmp/ecosboard/ecos/install/include/cyg/kernel/sched.hxx:397\n"
 #1  0x000088d0 in Cyg_Thread::exit () at
 /ecos-c/cygwin/tmp/ecosboard/ecos/install/include/cyg/kernel/sched.hxx:397
 &"Cannot access memory at address 0xdeadbeeb\n"
 Cannot access memory at address 0xdeadbeeb
 792^done
 (gdb) 
 
 Probably -stack-info-depth should report the number of successful
 frames found.
 
 -- 
 Daniel Jacobowitz
 CodeSourcery