From: Simon Marchi <simon.marchi@polymtl.ca>
To: LE GARREC Vincent <legarrec.vincent@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Run multiple parallel instances of gdb
Date: Sun, 11 Mar 2018 20:54:00 -0000 [thread overview]
Message-ID: <4b04209db0308576e68320a5d22181e4@polymtl.ca> (raw)
In-Reply-To: <CAH0JWTvJO7opYb=3ANZOiJG9KnJ+pDryMHP6mS5xoB2_V-BWEw@mail.gmail.com>
On 2018-03-11 16:15, LE GARREC Vincent wrote:
> 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
Hi Vincent,
Do you get a "suspended (tty output)" message? If so, what you have is
a background process trying to output on the terminal while the terminal
has the "tostop" flag set. A simpler case to reproduce it is:
$ gdb -batch -ex run --args /bin/echo salut &
[1] 28223
$
[1] + 28223 suspended (tty output) gdb -q -batch -ex run --args
/bin/echo salut
I don't understand why though, because my terminal does not have
"tostop" enabled:
$ stty
speed 38400 baud; line = 0;
-brkint -imaxbel iutf8
So something in the process probably sets that flag... Anyway, one way
to get around it is to change the terminal for the newly created
inferiors, for example to /dev/null if you don't need them to do I/O on
the terminal:
$ gdb -batch -ex "tty /dev/null" -ex run --args /bin/echo salut &
[1] 28276
$ [Inferior 1 (process 28285) exited normally]
[1] + 28276 done gdb -q -batch -ex "tty /dev/null" -ex run --args
/bin/echo salut
One comment below:
> [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);
You are missing the "do" from your do/while, which results in an
infinite loop here (if wait_pid is 0).
Simon
next prev parent reply other threads:[~2018-03-11 20:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-11 20:15 LE GARREC Vincent
2018-03-11 20:54 ` Simon Marchi [this message]
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=4b04209db0308576e68320a5d22181e4@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb@sourceware.org \
--cc=legarrec.vincent@gmail.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