From: Xingxing Pan <forandom@gmail.com>
To: gdb-patches@sourceware.org
Subject: Re: [patch] solib-display.exp: displays for local variables automatically disabled
Date: Tue, 09 Nov 2010 02:38:00 -0000 [thread overview]
Message-ID: <AANLkTim=PFcJpfBoLMqKfebLVxV1UMXfiz_VC++npJ-t@mail.gmail.com> (raw)
In-Reply-To: <20101108143618.GA30630@host0.dyn.jankratochvil.net>
Hi, Jan.
I'm using GDB 7.2, GCC 4.4.2, on an ARM similar arch.
I found that after the restart,
d->exp != NULL && d->exp->gdbarch != get_current_arch()
was asserted, which resulted in that d->exp was assigned NULL and parsed again.
For the local variables, because of out of scope, the parse was
failed, which resulted in d->enanble_p is assigned ZERO before the
warning.
For the globals, the parse would succeed.
Is it normal to have d->exp->gdbarch != get_current_arch() after restart?
Thanks,
Pan Xingxing
2010/11/8 Jan Kratochvil <jan.kratochvil@redhat.com>:
- 隐藏引用文字 -
> On Mon, 08 Nov 2010 14:19:18 +0100, Xingxing Pan wrote:
>> FAIL: gdb.base/solib-display.exp: NO: continue
>> FAIL: gdb.base/solib-display.exp: IN: continue
>> FAIL: gdb.base/solib-display.exp: SEP: continue
>
> But it PASSes for me on FSF GDB HEAD and x86_64-fedora14-linux-gnu.
>
>
>> warning: Unable to display "a_static": No symbol "a_static" in current context.
>
> This means `d->exp == NULL' in do_one_display. But the expression should be
> valid, inferior has been just restarted, not reloaded.
>
>
> Do you have info on your system to make the problem reproducible for me?
>
>
> Thanks,
> Jan
>
next prev parent reply other threads:[~2010-11-09 2:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-08 13:19 Xingxing Pan
2010-11-08 14:36 ` Jan Kratochvil
2010-11-09 2:38 ` Xingxing Pan [this message]
[not found] ` <AANLkTin3WfSRcmZnc2jke_Pebhp0dMM5V==0CJDBR87o@mail.gmail.com>
[not found] ` <20101109024617.GA20814@host0.dyn.jankratochvil.net>
2010-11-09 3:29 ` Xingxing Pan
2010-11-09 3:51 ` Jan Kratochvil
2010-11-09 5:40 ` Xingxing Pan
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='AANLkTim=PFcJpfBoLMqKfebLVxV1UMXfiz_VC++npJ-t@mail.gmail.com' \
--to=forandom@gmail.com \
--cc=gdb-patches@sourceware.org \
/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