Problem with -stack-list-frames

Daniel Jacobowitz drow@false.org
Wed Feb 11 19:03:00 GMT 2009


On Wed, Feb 11, 2009 at 09:57:15PM +0300, Vladimir Prus wrote:
> > -stack-list-frames
> > 
> > bt
> > #0  tmc_init () at qct\services\tmc\tmc.c:11541
> > #1  0x00c1d4c6 in tmc_task (ignored=<value optimized out>)
> >    at qct\services\tmc\tmc.c:12350
> > #2  0x00eee43e in rex_thread_init (entrypoint=0xc1d4a9 <tmc_task+1>)
> >    at qct\services\rexl4\rexl4.c:174
> > #3  0x00f3e0c8 in __thread_stub ()
> > #4  0x00f3e0c8 in __thread_stub ()
> > Backtrace stopped: previous frame identical to this frame (corrupt stack?)
> > 
> > As you can see, info threads and bt works as expected.
> 
> Please enable the verbose mode in the console -- there's a button in the
> toolbar. This will tell exactly what the error is -- and I'm 51% sure
> the problem is that you are trying to send MI command, and DSF thinks it's
> CLI command, and sends something not right.

Another possible problem is PR 9500, which I analyzed but never
fixed...

-- 
Daniel Jacobowitz
CodeSourcery



More information about the Gdb mailing list