Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#42892 - [linux] can't get backtraces on crashes

Attached to Project: Arch Linux
Opened by Matthias Krüger (matthiaskrgr) - Monday, 24 November 2014, 21:23 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Sunday, 07 December 2014, 04:39 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

The problem occurs since last reboot so I guess it's a kernel problem.

Name : linux
Version : 3.17.3-1

Name : gcc-multilib
Version : 4.9.2-1

Name : gdb
Version : 7.8.1-1

Name : glibc
Version : 2.20-3

When I run cppcheck with --exception-handling and make it crash, it just prints
zsh: segmentation fault (core dumped)

gdb didn't put out anything useful (yes, I compiled cppcheck with -g)

eading symbols from /home/matthias/vcs/github/cppcheck/cppcheck...sdone.
(gdb) start gcc/testsuite/g++.old-deja/g++.pt/ttp23.C
Temporary breakpoint 1 at 0x68f42f: file cli/main.cpp, line 120.
Starting program: /home/matthias/vcs/github/cppcheck/cppcheck gcc/testsuite/g++.old-deja/g++.pt/ttp23.C
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?

Temporary breakpoint 1, main (argc=2, argv=0x7fffffffe858) at cli/main.cpp:120
120 CppCheckExecutor exec;
(gdb) bt
#0 main (argc=2, argv=0x7fffffffe858) at cli/main.cpp:120
(gdb) bt-full
Undefined command: "bt-full". Try "help".
(gdb) bt full
#0 main (argc=2, argv=0x7fffffffe858) at cli/main.cpp:120
exec = {<ErrorLogger> = {_vptr.ErrorLogger = 0x8e5d65}, _settings = 0x7fffffffe6ff,
_errorList = std::__debug::set with 140737339737705 elements<error reading variable: Cannot access memory at address 0x48000019e5e8c799>, _files = std::__debug::map with 48 elements = {
[""] = 6768016<error reading variable: Cannot access memory at address 0x841f0f2e6676>...}, time1 = 9080336,
static exceptionOutput = "", errorlist = 144}


and -fsanitize=address builds also don't print anything like they did before.


Backtrace were fine before last reboot.
This task depends upon

Closed by  Gerardo Exequiel Pozzi (djgera)
Sunday, 07 December 2014, 04:39 GMT
Reason for closing:  Fixed
Additional comments about closing:  Seems to be resolved.
Comment by Matthias Krüger (matthiaskrgr) - Friday, 28 November 2014, 09:21 GMT
Still broken with kernel 3.17.4-1
Comment by Matthias Krüger (matthiaskrgr) - Friday, 28 November 2014, 22:18 GMT
It seems that clang -fsanitize=address builds get me a backtrace, so maybe be that gcc is the problem.
Comment by Matthias Krüger (matthiaskrgr) - Thursday, 04 December 2014, 19:45 GMT
Seems to be fixed by now.

Name : linux
Version : 3.17.4-1

Name : gcc-multilib
Version : 4.9.2-1

Name : gdb
Version : 7.8.1-1

Name : glibc
Version : 2.20-4

Loading...