Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: Tom Tromey <tromey@redhat.com>, gdb-patches@sourceware.org
Subject: Re: RFC: fix `gdb -write' case
Date: Wed, 11 May 2011 08:06:00 -0000	[thread overview]
Message-ID: <20110511080559.GA5358@host1.jankratochvil.net> (raw)
In-Reply-To: <4DC89CC7.4070402@codesourcery.com>

On Tue, 10 May 2011 04:02:47 +0200, Yao Qi wrote:
> Is this patch to fix bugs against gdb 6.8?

No.  In FSF gdb-6.8 it worked.  In FSF GDB HEAD it is broken.  It is
a regression.


> I am still unable to reproduce this problem on gdb 20110505-cvs.
> 
> $ ./gdb/gdb -nx -write ~/Work/gdb-write
> (gdb) set var s="b"
> evaluation of this expression requires the target program to be active

This worked with gdb-6.8, therefore you have reproduced the problem.


> (gdb) b main
> Breakpoint 1 at 0x80483b7: file gdb-write.c, line 3.
> (gdb) run
> Starting program: /home/yao/Work/gdb-write
> BFD: reopening /home/yao/Work/gdb-write: Text file busy
> 
> [This message above repeats]
> Breakpoint 1, main () at gdb-write.c:3
> 3	main(){return s[0]=='a';}
> (gdb) set var s="b"
> BFD: reopening /home/yao/Work/gdb-write: Text file busy
> ....
> Invalid cast.
> 
> Is it a separate issue?

This breaks for me a similar (but exactly the same) way with gdb-6.8.
I find this part as offtopic for this Bug.


Thanks,
Jan


  parent reply	other threads:[~2011-05-11  8:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-06 17:12 Tom Tromey
2011-05-09  3:11 ` Yao Qi
2011-05-09 14:54   ` Tom Tromey
2011-05-10  2:03     ` Yao Qi
2011-05-10 14:16       ` Tom Tromey
2011-05-11  8:06       ` Jan Kratochvil [this message]
2011-05-11 14:38     ` Jan Kratochvil
2011-05-11 19:42       ` Tom Tromey
2011-05-22 18:24         ` Jan Kratochvil
2011-05-23 20:24           ` Tom Tromey

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=20110511080559.GA5358@host1.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@redhat.com \
    --cc=yao@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