From: Daniel Jacobowitz <drow@false.org>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb@sources.redhat.com
Subject: Re: Problem with -stack-list-frames
Date: Wed, 11 Feb 2009 19:03:00 -0000 [thread overview]
Message-ID: <20090211190255.GA3060@caradoc.them.org> (raw)
In-Reply-To: <gmv72b$nf5$1@ger.gmane.org>
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
next prev parent reply other threads:[~2009-02-11 19:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 17:55 Dmitry Smirnov
2009-02-11 18:57 ` Vladimir Prus
2009-02-11 19:03 ` Daniel Jacobowitz [this message]
2009-02-11 19:09 ` Marc Khouzam
[not found] ` <6D19CA8D71C89C43A057926FE0D4ADAA067F0360@ecamlmw720.eamcs.ericsson.se>
2009-02-11 19:11 ` Marc Khouzam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090211190255.GA3060@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=vladimir@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox