Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: GDB <gdb-patches@sourceware.org>, Pedro Alves <pedro@codesourcery.com>
Subject: New gdbserver failures
Date: Mon, 12 Apr 2010 14:48:00 -0000	[thread overview]
Message-ID: <r2q6dc9ffc81004120748q7c6f114aq6fdeb798b78d26f5@mail.gmail.com> (raw)

On Linux/x86-64, I saw

FAIL: gdb.server/ext-attach.exp: attach to remote program 2
FAIL: gdb.server/ext-attach.exp: backtrace 2

They weren't there on April 11, 2010. I got

gnu-18:pts/4[18]> ./gdbserver-old --multi gnu-18:10000
Listening on port 10000
Remote debugging from host 172.25.70.137
readchar: Got EOF
Remote side has terminated connection.  GDBserver will reopen the connection.
Listening on port 10000
Remote debugging from host 172.25.70.137
Process 64 created; pid = 25716
Detaching from process 25716
1.100000
Cannot attach to lwp 25716: Operation not permitted (1)


-- 
H.J.


             reply	other threads:[~2010-04-12 14:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-12 14:48 H.J. Lu [this message]
2010-04-12 14:54 ` H.J. Lu
2010-04-12 15:00 ` Pedro Alves
2010-04-12 17:45   ` Pedro Alves

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=r2q6dc9ffc81004120748q7c6f114aq6fdeb798b78d26f5@mail.gmail.com \
    --to=hjl.tools@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@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