public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "dilyan.palauzov at aegee dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/16809] interrupt -a
Date: Sun, 13 Jul 2014 21:58:00 -0000	[thread overview]
Message-ID: <bug-16809-4717-9frxcvWMMk@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16809-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=16809

--- Comment #2 from dilyan.palauzov at aegee dot org <dilyan.palauzov at aegee dot org> ---
I use gdb-7.7.1 and the changes from
https://sourceware.org/ml/gdb-patches/2014-07/msg00304.html were already
applied.

In 7.7.1 I applied only the patch from gdb/infcmd.c on
interrupt_target_command(), because there is no interrupt_command().  I cannot
link gdb:

infcmd.o: In function `wait_thread_stopped':
gdb-7.7.1/gdb/infcmd.c:2818: undefined reference to `print_stop_event'
infcmd.o: In function `interrupt_target_command':
gdb-7.7.1/gdb/infcmd.c:2921: undefined reference to `prepare_execution_command'

Please provide patch toward gdb771.

Sample program, that leads to the described error:

#include <iostream>
#include <unistd.h>
#include <thread>

void f() {
  std::cout << "A" << std::endl;
  sleep (10);
  std::cout << "Z" << std::endl;
}

int main() {
  std::thread t1 { f }; std::thread t2 { f };
  std::thread t3 { f }; std::thread t4 { f };
  std::thread t5 { f }; std::thread t6 { f };
  std::thread t7 { f }; std::thread t8 { f };
  std::thread t9 { f }; std::thread t10 { f };
  std::thread t11 { f }; std::thread t12 { f };
  sleep (15);
  t1.join(); t2.join(); t3.join(); t4.join(); t5.join(); t6.join();
  t7.join(); t8.join(); t9.join(); t10.join(); t11.join(); t12.join();
}

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2014-07-13 21:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-04 20:00 [Bug gdb/16809] New: " dilyan.palauzov at aegee dot org
2014-07-12 19:02 ` [Bug gdb/16809] " xdje42 at gmail dot com
2014-07-13 21:58 ` dilyan.palauzov at aegee dot org [this message]
2014-07-13 23:30 ` dilyan.palauzov at aegee dot org
2014-07-14  0:19 ` xdje42 at gmail dot com
2014-07-14  0:30 ` xdje42 at gmail dot com
2014-07-14  0:51 ` xdje42 at gmail dot com
2014-07-14  3:10 ` xdje42 at gmail dot com
2014-07-15  6:18 ` dje at google dot com
2014-07-15  8:19 ` palves at redhat dot com
2014-07-15 19:48 ` dilyan.palauzov at aegee dot org
2014-07-15 19:58 ` xdje42 at gmail dot com
2014-07-15 19:59 ` xdje42 at gmail dot com
2014-07-15 21:21 ` palves at redhat dot com

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=bug-16809-4717-9frxcvWMMk@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).