From: Jonny Grant <jg@jguk.org>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: Florian Weimer <fw@deneb.enyo.de>, Andrew Haley <aph@redhat.com>,
Xi Ruoyao <xry111@mengyan1223.wang>,
gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Recursive SIGSEGV question
Date: Wed, 27 Mar 2019 23:51:00 -0000 [thread overview]
Message-ID: <490f5b68-a9a9-943e-6485-28c0fd51835d@jguk.org> (raw)
In-Reply-To: <CAH6eHdTuEb27hesYmacVNm7v0M__brk=28kxrgMQCmMxDhoeFQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2747 bytes --]
On 27/03/2019 21:34, Jonathan Wakely wrote:
> On Wed, 27 Mar 2019 at 21:27, Jonny Grant wrote:
>> Hi!
>>
>> Thank you for your reply and input.
>>
>> Maybe GCC's "libbacktrace" module could be used?
>>
>> I was wondering if -fsanitize=address would output a backtrace for the
>> C++ exception, but it doesn't seem to. Also it actually prevents the
>> core being dumped - that's probably not intended?
>>
>> Compile without Sanitizer, and it does dump the core to a file at least!
>>
>> $ export UBSAN_OPTIONS=print_stacktrace=1
>
> This is a UBsan option.
>
>> // g++-8 -fsanitize=address -Wall -o exception exception.cpp
>
> But you're not using UBsan.
>
>> #include <vector>
>> int main()
>> {
>> std::vector<int> v;
>> return v.at(0);
>> }
>>
>>
>> $ ./exception
>> terminate called after throwing an instance of 'std::out_of_range'
>> what(): vector::_M_range_check: __n (which is 0) >= this->size()
>> (which is 0)
>> Aborted
>
> There's no undefined behaviour or memory corruption here, so it's not
> surprising that UBsan and Asan don't print anything.
Ok I see, thank you for pointing this out.
I did wonder, as -fsanitize=address seems to inhibit the core dump that
is otherwise created by the abort() that appears to be called - is that
a known issue?
$ g++-8 -Wall -o exception exception.cpp
jonny@asus:~/code/crash$ ./exception
terminate called after throwing an instance of 'std::out_of_range'
what(): vector::_M_range_check: __n (which is 0) >= this->size()
(which is 0)
Aborted (core dumped)
$
Usually I just load the core dump into GDB to take a look at it.
> If you want a stack trace for exceptions that terminate the process
> then you could install a custom terminate handler which does that.
> Libstdc++'s default terminate handler just prints the message above,
> which includes the type of the exception and if it's a type derived
> from std::exception, the what() string stored in it.
Yes, I'd love to have a stack trace for exceptions that terminate the
process. Do you know a simple example you can refer me to? I've looked
and there are people using boost::stacktrace::stacktrace() but I'd
rather not link to boost as a dependency.
It would be great if there was a glibc option to do this, or GCC could
insert it.
Otherwise we each need to insert our own stack tracers...
Found this:
https://www.gnu.org/software/libc/manual/html_node/Backtraces.html
I added this (attached) to a C++ exception handler, but there's no file
and line numbers. Other examples resort to calling addr2line! Seems a
bit over the top for us each to code our own stack tracer... Or reading
symbols etc. Am I asking too much for a general print_backtrace() in
libc or elsewhere ?
Cheers, Jonny
[-- Attachment #2: exception.cpp --]
[-- Type: text/x-c++src, Size: 897 bytes --]
// g++-8 -Wall -g -o exception exception.cpp
#include <vector>
#include <iostream>
int main2();
#include <execinfo.h>
#include <stdio.h>
#include <stdlib.h>
/* Obtain a backtrace and print it to stdout.
https://www.gnu.org/software/libc/manual/html_node/Backtraces.html
*/
void
print_trace (void)
{
void *array[10];
size_t size;
char **strings;
size_t i;
size = backtrace (array, 10);
strings = backtrace_symbols (array, size);
printf ("Obtained %zd stack frames.\n", size);
for (i = 0; i < size; i++)
printf ("symbols %s\n", strings[i]);
free (strings);
}
int main()
{
try
{
main2();
}
catch( const std::exception &e)
{
const std::string what(e.what());
std::cout << "Unhandled exception: [" << what << "]\n";
print_trace();
exit(0);
}
}
int main2()
{
std::vector<int> v;
return v.at(0);
}
next prev parent reply other threads:[~2019-03-27 23:47 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 22:05 Jonny Grant
2019-03-20 4:02 ` Florian Weimer
2019-03-20 8:11 ` Jonny Grant
2019-03-25 13:23 ` Jonny Grant
2019-03-25 13:27 ` Jonathan Wakely
2019-03-25 13:56 ` Florian Weimer
2019-03-25 14:01 ` Xi Ruoyao
2019-03-25 15:47 ` Florian Weimer
2019-03-25 16:10 ` Andrew Haley
2019-03-25 16:13 ` Jonny Grant
2019-03-25 16:23 ` Jonathan Wakely
2019-03-25 18:51 ` Florian Weimer
2019-03-25 20:39 ` Jonny Grant
2019-03-26 6:50 ` Xi Ruoyao
2019-03-27 0:29 ` Jonathan Wakely
2019-03-27 21:34 ` Jonny Grant
2019-03-27 23:43 ` Jonathan Wakely
2019-03-27 23:51 ` Jonny Grant [this message]
2019-03-28 8:26 ` Xi Ruoyao
2019-03-28 11:52 ` Jonathan Wakely
2019-03-29 2:24 ` Jonny Grant
2019-03-30 17:32 ` Jonny Grant
2023-02-19 21:21 ` Jonny Grant
2023-02-19 21:34 ` Jonny Grant
2019-03-28 13:55 ` Jonathan Wakely
2019-03-28 14:39 ` Jonny Grant
2019-03-28 14:39 ` Jonathan Wakely
2019-03-25 20:28 ` Segher Boessenkool
2019-03-25 18:56 ` Segher Boessenkool
2019-03-25 22:05 ` Jonny Grant
2019-03-26 10:20 ` Xi Ruoyao
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=490f5b68-a9a9-943e-6485-28c0fd51835d@jguk.org \
--to=jg@jguk.org \
--cc=aph@redhat.com \
--cc=fw@deneb.enyo.de \
--cc=gcc-help@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--cc=xry111@mengyan1223.wang \
/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).