Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: LE GARREC Vincent <legarrec.vincent@gmail.com>
To: gdb@sourceware.org
Subject: Run multiple parallel instances of gdb
Date: Sun, 11 Mar 2018 20:15:00 -0000	[thread overview]
Message-ID: <CAH0JWTvJO7opYb=3ANZOiJG9KnJ+pDryMHP6mS5xoB2_V-BWEw@mail.gmail.com> (raw)

Hi everybody,

I would like to sort crashes found by fuzzing. So I have around 1000 files
that make my application crashes. I made a small program to run gdb and to
extract backtraces to file. To increase speed, I run parallel instances.

Problem, with parallel instances, my program stopped. It doesn't crashes,
it stops. I have to run "fg" from terminal to continue and it's happening
very often. So actually, I'm running with single thread.

Is it normal ? Did I do something wrong ? If you need more information, I
can give you.

Please find after simple steps to reproduce the case,

Thanks for you advices,

Vincent Le Garrec

[1] : crash program
main.c (in /tmp folder)

int main()
{
  int *t = 0xDEADBEEF;
  *t = 1;
}

Run it and it should crash.

[2] : multiple execution of gdb
loopgdb.cpp

#include <thread>
#include <future>
#include <vector>
#include <functional>
#include <unistd.h>
#include <iostream>
#include <sys/types.h>
#include <sys/wait.h>

void run_gdb()
{
  pid_t child_pid = fork();
  std::cout << "run" << std::endl;
  if (child_pid != 0)
  {
    pid_t wait_pid;
    {
      wait_pid = waitpid(child_pid, nullptr, WNOHANG);
      sleep(1);
    }
    while(wait_pid == 0);
  }
  else
  {
    execlp("/usr/bin/gdb", "-batch-silent", "-ex", "run", "-ex", "set
logging overwrite on", "-ex", "set logging on", "-ex", "set pagination
off", "-ex", "handle SIG33 pass nostop noprint", "-ex", "backtrace full",
"-ex", "set logging off", "-ex", "quit", "--args", "/tmp/main", nullptr);
  }
}

int main()
{
  int nthreads = std::thread::hardware_concurrency();
  std::vector<std::future<void>> threads(nthreads);
  for (size_t t = 0; t < nthreads; t++)
  {
    threads[t] = std::async(std::launch::async, std::bind(
        []() {
          while(true)
          {
            run_gdb();
          }
        }));
  }
  for (std::future<void> & t : threads)
  {
    t.get();
  }

}

Run it (g++ loopgdb.cpp -o loopgdb -lpthread) and you will see that the
program in command-line will stopped.

[3] gdb --version
GNU gdb (Gentoo 8.1 p1) 8.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html
>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://bugs.gentoo.org/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".


             reply	other threads:[~2018-03-11 20:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-11 20:15 LE GARREC Vincent [this message]
2018-03-11 20:54 ` Simon Marchi
2018-03-11 21:37   ` LE GARREC Vincent
2018-03-11 22:57   ` Andreas Schwab

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='CAH0JWTvJO7opYb=3ANZOiJG9KnJ+pDryMHP6mS5xoB2_V-BWEw@mail.gmail.com' \
    --to=legarrec.vincent@gmail.com \
    --cc=gdb@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