Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #990571
| From | Bernhard Übelacker <bernhardu@mailbox.org> |
|---|---|
| Newsgroups | linux.debian.bugs.dist |
| Subject | Bug#948287: bash: *** stack smashing detected *** ( SIGABRT crash ) |
| Date | 2020-01-09 20:30 +0100 |
| Message-ID | <zmLFf-8i4-1@gated-at.bofh.it> (permalink) |
| References | (2 earlier) <zmIxH-6sR-3@gated-at.bofh.it> <zmIR4-6zG-13@gated-at.bofh.it> <zmJtL-72j-7@gated-at.bofh.it> <zlBRD-6mV-7@gated-at.bofh.it> <zmJtL-72j-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Am 09.01.20 um 17:56 schrieb crvi c: > I am using the same bash / gnome-terminal as part of my daily work. The > crash was random and it is not consistently reproducible. I have a > couple of bash core files, if that would be of any help. Ok, I see - had hoped it to be better reproducible. In my tests I found that the function in question get executed if I do for example "ls /" and tab. Could be the crashing cases are related to absolute paths? Otherwise you could try to run it by valgrind e.g. like following: valgrind --tool=memcheck --trace-children=no --child-silent-after-fork=yes bash valgrind --tool=exp-sgcheck --trace-children=no --child-silent-after-fork=yes bash Another approach could be, if CPU support is given, to use a timetravel debugger like rr to record bash executions and replay a crashing one to find out where the stack canary got overwritten. Unfortunately a core did alreay run over the interesting instruction changing that stack canary, will therefore not of so much use. Maybe just if the stack would be overwritten with some recognizable values ... Kind regards, Bernhard
Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Bug#948287: bash: *** stack smashing detected *** ( SIGABRT crash ) crvi <crvisqr@gmail.com> - 2020-01-06 15:50 +0100
Bug#948287: crash backtrace crvi c <crvisqr@gmail.com> - 2020-01-06 16:00 +0100
Bug#948287: bash: *** stack smashing detected *** ( SIGABRT crash ) Bernhard Übelacker <bernhardu@mailbox.org> - 2020-01-07 17:10 +0100
Bug#948287: bash: *** stack smashing detected *** ( SIGABRT crash ) crvi c <crvisqr@gmail.com> - 2020-01-09 17:10 +0100
Bug#948287: bash: *** stack smashing detected *** ( SIGABRT crash ) Bernhard Übelacker <bernhardu@mailbox.org> - 2020-01-09 17:30 +0100
Bug#948287: bash: *** stack smashing detected *** ( SIGABRT crash ) crvi c <crvisqr@gmail.com> - 2020-01-09 18:10 +0100
Bug#948287: bash: *** stack smashing detected *** ( SIGABRT crash ) Bernhard Übelacker <bernhardu@mailbox.org> - 2020-01-09 20:30 +0100
Bug#948287: bash: *** stack smashing detected *** ( SIGABRT crash ) Bernhard Übelacker <bernhardu@mailbox.org> - 2020-02-03 21:40 +0100
csiph-web