From: Andreas Schwab <schwab@suse.de>
To: Mahmood Naderan <nt_mahmood@yahoo.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: pt-raise.c: No such file or directory
Date: Tue, 12 Feb 2013 09:10:00 -0000 [thread overview]
Message-ID: <mvmhalh6goh.fsf@hawking.suse.de> (raw)
In-Reply-To: <1360659215.2000.YahooMailNeo@web163001.mail.bf1.yahoo.com> (Mahmood Naderan's message of "Tue, 12 Feb 2013 00:53:35 -0800 (PST)")
Mahmood Naderan <nt_mahmood@yahoo.com> writes:
>>This is only a warning, and you can safely ignore it.
>
> But the problem is as soon as I run "c" in gdb I receive a crash
> signal. You may say that my own program has problem, but on the other
> terminal, my program still waits for the continue message from gdb. Here
> is the output of gdb
>
> 0x00007fc740e65b7b in raise (sig=<optimized out>) at
> ../nptl/sysdeps/unix/sysv/linux/pt-raise.c:42
> 42Â Â Â Â Â ../nptl/sysdeps/unix/sysv/linux/pt-raise.c: No such file or
> directory.
> (gdb) c
> Continuing.
>
> Program received signal SIGSTOP, Stopped (signal).
Isn't that the signal the program is raising?
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2013-02-12 9:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 18:27 Mahmood Naderan
2013-02-11 19:13 ` Joel Brobecker
2013-02-12 8:53 ` Mahmood Naderan
2013-02-12 9:10 ` Andreas Schwab [this message]
2013-02-12 10:38 ` Mahmood Naderan
2013-02-12 10:50 ` Mahmood Naderan
2013-02-12 10:50 ` Andreas Schwab
2013-02-12 13:49 ` Mahmood Naderan
2013-02-12 21:31 ` Sergio Durigan Junior
2013-02-13 5:34 ` Mahmood Naderan
2014-05-20 10:19 Mahmood Naderan
2014-05-20 10:37 ` Jan Kratochvil
2014-05-20 10:45 ` Mahmood Naderan
2014-05-20 12:38 ` Jan Kratochvil
2014-05-20 20:22 ` Mahmood Naderan
2014-05-20 12:01 ` 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=mvmhalh6goh.fsf@hawking.suse.de \
--to=schwab@suse.de \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=nt_mahmood@yahoo.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