Bug#870728: [Pkg-mc-devel] Bug#870728: mc: random crash on startup (SIGSEGV)

2017-08-07 Thread Yury V. Zaytsev
Hi Paul, On Sun, 6 Aug 2017, Paul Wise wrote: On Sun, 2017-08-06 at 11:51 +0200, Yury V. Zaytsev wrote: We have a patch that you could try, it would be great if you could tell whether this fixes the problem for you:

Bug#870728: [Pkg-mc-devel] Bug#870728: mc: random crash on startup (SIGSEGV)

2017-08-06 Thread Paul Wise
On Sun, 2017-08-06 at 11:51 +0200, Yury V. Zaytsev wrote: > We have a patch that you could try, it would be great if you could tell  > whether this fixes the problem for you: > > http://midnight-commander.org/attachment/ticket/3846/3846_mcview_hook.patch Thanks, that fixes the problem. > The

Bug#870728: [Pkg-mc-devel] Bug#870728: mc: random crash on startup (SIGSEGV)

2017-08-06 Thread Yury V. Zaytsev
Hi Paul, We have a patch that you could try, it would be great if you could tell whether this fixes the problem for you: http://midnight-commander.org/attachment/ticket/3846/3846_mcview_hook.patch On Sat, 5 Aug 2017, Paul Wise wrote: On Fri, 2017-08-04 at 23:20 +0200, Yury V. Zaytsev

Bug#870728: [Pkg-mc-devel] Bug#870728: mc: random crash on startup (SIGSEGV)

2017-08-05 Thread Paul Wise
On Fri, 2017-08-04 at 23:20 +0200, Yury V. Zaytsev wrote: > The most obvious reason for the segfault would have been that somebody has  > freed `view->filename_vpath` without setting it to NULL, but a quick grep  > for `->filename_vpath` doesn't reveal anything suspicious :-( Discussion on IRC

Bug#870728: [Pkg-mc-devel] Bug#870728: mc: random crash on startup (SIGSEGV)

2017-08-05 Thread Denis Briand
Oops its ctrl+x q of course :)   Message d'origine   De: Yury V. Zaytsev Envoyé: samedi 5 août 2017 10:09 À: Denis Briand Cc: bug Objet: Re: [Pkg-mc-devel] Bug#870728: mc: random crash on startup (SIGSEGV) On Sat, 5 Aug 2017, Denis Briand wrote: > On Sat, Aug 05, 2017 at 12:07:39AM +0200, Y

Bug#870728: [Pkg-mc-devel] Bug#870728: mc: random crash on startup (SIGSEGV)

2017-08-05 Thread Yury V. Zaytsev
On Sat, 5 Aug 2017, Denis Briand wrote: On Sat, Aug 05, 2017 at 12:07:39AM +0200, Yury V. Zaytsev wrote: On Fri, 4 Aug 2017, Denis Briand wrote: No I can't reproduce it with git master master and the sid version, because the start is too quick... ^^ My valgrind report is clean. I attached

Bug#870728: [Pkg-mc-devel] Bug#870728: mc: random crash on startup (SIGSEGV)

2017-08-04 Thread Denis Briand
On Sat, Aug 05, 2017 at 12:07:39AM +0200, Yury V. Zaytsev wrote: > On Fri, 4 Aug 2017, Denis Briand wrote: > > >No I can't reproduce it with git master master and the sid version, > >because the start is too quick... ^^ My valgrind report is clean. I > >attached the Paul valgrind report on the

Bug#870728: [Pkg-mc-devel] Bug#870728: mc: random crash on startup (SIGSEGV)

2017-08-04 Thread Yury V. Zaytsev
On Fri, 4 Aug 2017, Denis Briand wrote: No I can't reproduce it with git master master and the sid version, because the start is too quick... ^^ My valgrind report is clean. I attached the Paul valgrind report on the upstream bug ticket. Well, it claims that the memory that viewer filename

Bug#870728: [Pkg-mc-devel] Bug#870728: mc: random crash on startup (SIGSEGV)

2017-08-04 Thread Denis Briand
On Fri, Aug 04, 2017 at 11:29:43PM +0200, Yury V. Zaytsev wrote: > On Fri, 4 Aug 2017, Denis Briand wrote: > > >Step to reproduce: > >$ MALLOC_PERTURB_=254 MALLOC_CHECK_=2 mc > >then during the startup: hit "Ctrl+x g" keys combo > > > >Important: you must hit "Ctrl+x g" keys before the panels are

Bug#870728: [Pkg-mc-devel] Bug#870728: mc: random crash on startup (SIGSEGV)

2017-08-04 Thread Yury V. Zaytsev
On Fri, 4 Aug 2017, Denis Briand wrote: Step to reproduce: $ MALLOC_PERTURB_=254 MALLOC_CHECK_=2 mc then during the startup: hit "Ctrl+x g" keys combo Important: you must hit "Ctrl+x g" keys before the panels are displayed. To reproduce this long start, you have got 370 sub-directories in the

Bug#870728: [Pkg-mc-devel] Bug#870728: mc: random crash on startup (SIGSEGV)

2017-08-04 Thread Yury V. Zaytsev
Hi Paul, Thanks for the report! To be very honest, I'm not sure how actionable it is though :-/ The most obvious reason for the segfault would have been that somebody has freed `view->filename_vpath` without setting it to NULL, but a quick grep for `->filename_vpath` doesn't reveal anything

Bug#870728: mc: random crash on startup (SIGSEGV)

2017-08-04 Thread Denis Briand
severity 870728 minor forwarded 870728 https://midnight-commander.org/ticket/3846 thanks Thank you Paul. As I said on IRC, it is a very particular case. So I switch this bug to minor and I forward it to upstream. To summarize here our IRC chat: Step to reproduce: $ MALLOC_PERTURB_=254

Bug#870728: mc: random crash on startup (SIGSEGV)

2017-08-04 Thread Paul Wise
On Fri, 2017-08-04 at 12:51 -0400, Paul Wise wrote: > I should note that I have these variables set. I expect the > 0xfefefefefefefefe in the traceback is from the second one. This is confirmed: $ strings /var/crash/1000/5115-1000-1000-11-1501856299-chianamo--usr-bin-mc.core | grep MALLOC

Bug#870728: mc: random crash on startup (SIGSEGV)

2017-08-04 Thread Paul Wise
On Fri, 2017-08-04 at 10:53 -0400, Paul Wise wrote: > I got a random crash when starting mc: I should note that I have these variables set. I expect the 0xfefefefefefefefe in the traceback is from the second one. #

Bug#870728: mc: random crash on startup (SIGSEGV)

2017-08-04 Thread Paul Wise
Package: mc Version: 3:4.8.18-1 Severity: normal Usertags: crash I got a random crash when starting mc: $ gdb -batch -n -ex 'set pagination off' -ex bt -ex 'thread apply all bt full' --core /var/crash/1000/5115-1000-1000-11-1501856299-chianamo--usr-bin-mc.core /usr/bin/mc [New LWP 5115]