Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
In order to test that coredumps are generated and that they contain useful information which can be retreived with gdb I need to generate a SIGSEGV. Or anything else which causes a coredump. The co...
#4: Post edited
by
Estela
·
2020-08-31T12:27:08Z (over 4 years ago)
- In order to test that coredumps are generated and that they contain useful information which can be retreived with gdb I need to generate a SIGSEGV. Or anything else which causes a coredump.
- The code I am using is:
- int *p = nullptr;
- *p = 0;
- Which works fine but is undefined behaviour. It might as well not generate a SIGSEGV at all.
As expected the draft of the C++ standard I've checked does not contain the SIGSEGV word at all. So there must be no portable way to do so. Is there an implementation specific documented way to do so with gcc?
- In order to test that coredumps are generated and that they contain useful information which can be retreived with gdb I need to generate a SIGSEGV. Or anything else which causes a coredump.
- The code I am using is:
- int *p = nullptr;
- *p = 0;
- Which works fine but is undefined behaviour. It might as well not generate a SIGSEGV at all.
- Is there a portable way to raise that signal? And if not, is there an implementation specific documented way to do so with gcc?
#3: Post edited
by
Estela
·
2020-08-31T10:04:49Z (over 4 years ago)
Generate SIGSEV without undefined behaviour.
- Generate SIGSEGV without undefined behaviour.
In order to test that coredumps are generated and that they contain useful information which can be retreived with gdb I need to generate a SIGSEV. Or anything else which causes a coredump.- The code I am using is:
- int *p = nullptr;
- *p = 0;
Which works fine but is undefined behaviour. It might as well not generate a SIGSEV at all.As expected the draft of the C++ standard I've checked does not contain the SIGSEV word at all. So there must be no portable way to do so. Is there an implementation specific documented way to do so with gcc?
- In order to test that coredumps are generated and that they contain useful information which can be retreived with gdb I need to generate a SIGSEGV. Or anything else which causes a coredump.
- The code I am using is:
- int *p = nullptr;
- *p = 0;
- Which works fine but is undefined behaviour. It might as well not generate a SIGSEGV at all.
- As expected the draft of the C++ standard I've checked does not contain the SIGSEGV word at all. So there must be no portable way to do so. Is there an implementation specific documented way to do so with gcc?
#2: Post edited
by
Estela
·
2020-08-31T09:52:53Z (over 4 years ago)
In order to test that coredumps are generated and that they contain useful information which can be retreived with gdb I need to generate a SIGSEV. Or anything else which uses a coredump.- The code I am using is:
- int *p = nullptr;
- *p = 0;
- Which works fine but is undefined behaviour. It might as well not generate a SIGSEV at all.
- As expected the draft of the C++ standard I've checked does not contain the SIGSEV word at all. So there must be no portable way to do so. Is there an implementation specific documented way to do so with gcc?
- In order to test that coredumps are generated and that they contain useful information which can be retreived with gdb I need to generate a SIGSEV. Or anything else which causes a coredump.
- The code I am using is:
- int *p = nullptr;
- *p = 0;
- Which works fine but is undefined behaviour. It might as well not generate a SIGSEV at all.
- As expected the draft of the C++ standard I've checked does not contain the SIGSEV word at all. So there must be no portable way to do so. Is there an implementation specific documented way to do so with gcc?
#1: Initial revision
by
Estela
·
2020-08-31T09:51:08Z (over 4 years ago)
Generate SIGSEV without undefined behaviour.
In order to test that coredumps are generated and that they contain useful information which can be retreived with gdb I need to generate a SIGSEV. Or anything else which uses a coredump.
The code I am using is:
int *p = nullptr;
*p = 0;
Which works fine but is undefined behaviour. It might as well not generate a SIGSEV at all.
As expected the draft of the C++ standard I've checked does not contain the SIGSEV word at all. So there must be no portable way to do so. Is there an implementation specific documented way to do so with gcc?