From: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
To: gdb-patches@sources.redhat.com
Subject: PATCH: Make gdbserver use async I/O on Linux
Date: Wed, 06 Jun 2001 14:03:00 -0000 [thread overview]
Message-ID: <20010606140322.A29266@nevyn.them.org> (raw)
The only problem I can think of that this might cause is if F_SETOWN is less
portable than FASYNC. Apparently you need to do that explicitly on a Linux
target before SIGIO will be sent.
This lets C-c on the host be properly handled, stopping the target.
--
Daniel Jacobowitz Debian GNU/Linux Developer
Monta Vista Software Debian Security Team
From ezannoni@cygnus.com Wed Jun 06 14:10:00 2001
From: Elena Zannoni <ezannoni@cygnus.com>
To: Jim Blandy <jimb@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: Properly detect that GDB was compiled without MI support
Date: Wed, 06 Jun 2001 14:10:00 -0000
Message-id: <15134.39998.848755.666987@kwikemart.cygnus.com>
References: <20010605210124.AABD95E9CB@zwingli.cygnus.com>
X-SW-Source: 2001-06/msg00097.html
Content-length: 1679
Jim, I must be seeing double, but I think this output is already
handled in the -re directly below the one you changed.
(Ok I am jet-lagged, so excuse me if I am wrong).
-re ".*unrecognized option.*for a complete list of options." {
untested "Skip mi tests (not compiled with mi support)."
remote_close host;
return -1;
}
-re ".*Interpreter `mi' unrecognized." {
untested "Skip mi tests (not compiled with mi support)."
remote_close host;
return -1;
}
Elena
Jim Blandy writes:
>
> gdb/testsuite/gdb.mi/ChangeLog-mi:
>
> 2001-06-05 Jim Blandy <jimb@redhat.com>
>
> * lib/mi-support.exp: Recognize new error message, indicating that GDB
> was compiled without MI support.
>
> Index: gdb/testsuite/lib/mi-support.exp
> ===================================================================
> RCS file: /cvs/cvsfiles/devo/gdb/testsuite/lib/mi-support.exp,v
> retrieving revision 1.24
> diff -c -r1.24 mi-support.exp
> *** gdb/testsuite/lib/mi-support.exp 2001/01/15 12:28:02 1.24
> --- gdb/testsuite/lib/mi-support.exp 2001/06/05 20:57:06
> ***************
> *** 130,136 ****
> remote_close host;
> return -1;
> }
> ! -re ".*unrecognized option.*for a complete list of options." {
> untested "Skip mi tests (not compiled with mi support)."
> remote_close host;
> return -1;
> --- 130,136 ----
> remote_close host;
> return -1;
> }
> ! -re ".*(unrecognized option.*for a complete list of options.)|(Interpreter `mi' unrecognized)" {
> untested "Skip mi tests (not compiled with mi support)."
> remote_close host;
> return -1;
>
next reply other threads:[~2001-06-06 14:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-06 14:03 Daniel Jacobowitz [this message]
2001-06-06 23:34 ` Eli Zaretskii
2001-06-07 10:43 ` Daniel Jacobowitz
2001-06-07 11:38 ` Eli Zaretskii
2001-06-07 12:04 ` Daniel Jacobowitz
2001-06-08 0:37 ` Eli Zaretskii
2001-06-21 13:28 ` J.T. Conklin
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=20010606140322.A29266@nevyn.them.org \
--to=dmj+@andrew.cmu.edu \
--cc=gdb-patches@sources.redhat.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