bugWeeChat - Bugs: bug #41735, When I close, I get an error, but...

 
 

bug #41735: When I close, I get an error, but everything works correctly

Submitter:  None
Submitted:  Fri 28 Feb 2014 06:47:13 PM UTC
   
 
Category:  other Severity:  3 - Normal
Item Group:  crash Status:  Need Info
Privacy:  Public Assigned to:  flashcode
Originator Name:  Brandon Turk Originator Email:  * -email is unavailable-
Open/Closed:  Open Release:  * 3.3-dev
IRC nick: 
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Fri 04 Apr 2014 04:54:13 PM UTC, comment #7: 


>Are you using latest devel version, compiled with CMake?

Yes.

>If still not working with devel compiled with CMake, please try to start WeeChat without scripts (weechat -s). Does it still crash without scripts?

Yes.

I've also tried reinstalling all my dependencies and doing it as you asked and still get the crash.
I've also tried installing using homebrew (instead of compiling on my own) using flags "--with-aspell --with-guile --with-lua --with-perl --with-python --with-ruby --HEAD" and still get the crash on exit.

Every backtrace is the exact same.

Anonymous
Fri 04 Apr 2014 04:06:12 PM UTC, comment #6: 

Are you using latest devel version, compiled with CMake?
If not, please try that (a bug with threads was fixed some weeks ago, but in CMake only, not configure).

If still not working with devel compiled with CMake, please try to start WeeChat without scripts (weechat -s). Does it still crash without scripts?

Sebastien Helleu <flashcode>
Group administrator
Tue 01 Apr 2014 04:37:07 AM UTC, comment #5: 

After fixing a few cmake things, I still crash on closing, but there's significantly less "frame #n":

$ lldb /usr/local/bin/weechat
Current executable set to '/usr/local/bin/weechat' (x86_64).
(lldb) target create --core /cores/core.86805
warning: (x86_64) /cores/core.86805 load command 279 LC_SEGMENT_64 has a fileoff + filesize (0x1cf14000) that extends beyond the end of the file (0x1cf13000), the segment will be truncated to match
warning: (x86_64) /cores/core.86805 load command 280 LC_SEGMENT_64 has a fileoff (0x1cf14000) that extends beyond the end of the file (0x1cf13000), ignoring this section
Core file '/cores/core.86805' (x86_64) was loaded.
Process 0 stopped

  • thread #1: tid = 0x0000, 0x00007fff86527866 libsystem_kernel.dylib`__pthread_kill + 10, stop reason = signal SIGSTOP

    frame #0: 0x00007fff86527866 libsystem_kernel.dylib`__pthread_kill + 10
libsystem_kernel.dylib`__pthread_kill + 10:
-> 0x7fff86527866:  jae    0x7fff86527870            ; __pthread_kill + 20
   0x7fff86527868:  movq   %rax, %rdi
   0x7fff8652786b:  jmpq   0x7fff86524175            ; cerror_nocancel
   0x7fff86527870:  ret
  thread #2: tid = 0x0001, 0x00007fff8652894a libsystem_kernel.dylib`poll + 10, stop reason = signal SIGSTOP
    frame #0: 0x00007fff8652894a libsystem_kernel.dylib`poll + 10
libsystem_kernel.dylib`poll + 10:
-> 0x7fff8652894a:  jae    0x7fff86528954            ; poll + 20
   0x7fff8652894c:  movq   %rax, %rdi
   0x7fff8652894f:  jmpq   0x7fff8652419a            ; cerror
   0x7fff86528954:  ret
(lldb) thread backtrace all

  • thread #1: tid = 0x0000, 0x00007fff86527866 libsystem_kernel.dylib`__pthread_kill + 10, stop reason = signal SIGSTOP

  * frame #0: 0x00007fff86527866 libsystem_kernel.dylib`__pthread_kill + 10
    frame #1: 0x00007fff891ee35c libsystem_pthread.dylib`pthread_kill + 92
    frame #2: 0x00007fff81f07b1a libsystem_c.dylib`abort + 125
    frame #3: 0x000000010a91e1e4 weechat`weechat_shutdown + 148
    frame #4: 0x000000010a94d9bd weechat`debug_sigsegv + 381
    frame #5: 0x00007fff875595aa libsystem_platform.dylib`_sigtramp + 26
    frame #6: 0x000000010af5e4a4
    frame #7: 0x00007fff6289da15 dyld`dyld::garbageCollectImages() + 634
    frame #8: 0x00007fff628a49d7 dyld`dlclose + 134
    frame #9: 0x00007fff8524479f libdyld.dylib`dlclose + 61
    frame #10: 0x000000010a918670 weechat`plugin_remove + 336
    frame #11: 0x000000010a918abb weechat`plugin_unload + 139
    frame #12: 0x000000010a918c30 weechat`plugin_unload_all + 80
    frame #13: 0x000000010a918f97 weechat`plugin_end + 23
    frame #14: 0x000000010a91e911 weechat`main + 577

  thread #2: tid = 0x0001, 0x00007fff8652894a libsystem_kernel.dylib`poll + 10, stop reason = signal SIGSTOP
    frame #0: 0x00007fff8652894a libsystem_kernel.dylib`poll + 10
    frame #1: 0x000000010c61a6e7 libruby.2.1.0.dylib`thread_timer + 288
    frame #2: 0x00007fff891ed899 libsystem_pthread.dylib`_pthread_body + 138
    frame #3: 0x00007fff891ed72a libsystem_pthread.dylib`_pthread_start + 137

Anonymous
Tue 01 Apr 2014 03:56:04 AM UTC, comment #4: 

I'm not sure if this will help, but I got lldb to give a backtrace:

  • thread #1: tid = 0x0000, 0x00007fff86527866 libsystem_kernel.dylib`__pthread_kill + 10, stop reason = signal SIGSTOP

  * frame #0: 0x00007fff86527866 libsystem_kernel.dylib`__pthread_kill + 10
    frame #1: 0x00007fff891ee35c libsystem_pthread.dylib`pthread_kill + 92
    frame #2: 0x00007fff81f07b1a libsystem_c.dylib`abort + 125
    frame #3: 0x00007fff81f07c91 libsystem_c.dylib`abort_report_np + 181
    frame #4: 0x00007fff81f2b860 libsystem_c.dylib`__chk_fail + 48
    frame #5: 0x00007fff81f2b830 libsystem_c.dylib`__chk_fail_overflow + 16
    frame #6: 0x00007fff81f2bbec libsystem_c.dylib`__strcat_chk + 121
    frame #7: 0x0000000106d80e2e python.so`weechat_python_output + 718
    frame #8: 0x0000000106ddef72 Python`PyObject_Call + 101
    frame #9: 0x0000000106e5b01f Python`PyEval_CallObjectWithKeywords + 93
    frame #10: 0x0000000106df5732 Python`PyFile_WriteObject + 380
    frame #11: 0x0000000106df58c2 Python`PyFile_WriteString + 241
    frame #12: 0x0000000106e74661 Python`PyErr_Display + 1115
    frame #13: 0x0000000106e79d80 Python`___lldb_unnamed_function1637$$Python + 75
    frame #14: 0x0000000106ddef72 Python`PyObject_Call + 101
    frame #15: 0x0000000106e5b01f Python`PyEval_CallObjectWithKeywords + 93
    frame #16: 0x0000000106e73eed Python`PyErr_PrintEx + 227
    frame #17: 0x0000000106d7de8e python.so`weechat_python_exec + 1022
    frame #18: 0x0000000106d82577 python.so`weechat_python_api_hook_process_cb + 407
    frame #19: 0x0000000105cbb068 weechat`hook_process_send_buffers + 328
    frame #20: 0x0000000105cbb418 weechat`hook_process_timer_cb + 312
    frame #21: 0x0000000105cb8b88 weechat`hook_timer_exec + 264
    frame #22: 0x0000000105c2ef88 weechat`gui_main_loop + 200
    frame #23: 0x0000000105c7f983 weechat`main + 563

  thread #2: tid = 0x0001, 0x00007fff8652894a libsystem_kernel.dylib`poll + 10, stop reason = signal SIGSTOP
    frame #0: 0x00007fff8652894a libsystem_kernel.dylib`poll + 10
    frame #1: 0x000000010786b6e7 libruby.2.1.0.dylib`thread_timer + 288
    frame #2: 0x00007fff891ed899 libsystem_pthread.dylib`_pthread_body + 138
    frame #3: 0x00007fff891ed72a libsystem_pthread.dylib`_pthread_start + 137

Anonymous
Sun 30 Mar 2014 09:41:32 AM UTC, comment #3: 

Closing the bug, if ever you have more info, please let me know.

Sebastien Helleu <flashcode>
Group administrator
Sun 30 Mar 2014 09:39:15 AM UTC, comment #2: 

I could not debug the problem. GDB doesn't work properly on OSX Mavericks and could not get it to give the backtrace.

Anonymous
Sun 02 Mar 2014 10:03:30 PM UTC, comment #1: 

Could you please compile WeeChat with debug, and get a backtrace using gdb?

You can look at user's guide for more info: http://weechat.org/files/doc/devel/weechat_user.en.html#report_crashes

Sebastien Helleu <flashcode>
Group administrator
Fri 28 Feb 2014 06:47:13 PM UTC, original submission:  

As I said in the summary, this error pops up on every /quit, but it's not like anything is amiss, everything works as they're supposed to.

======= WeeChat backtrace =======
(written by WeeChat 0.4.4-dev, compiled on Feb 27 2014 09:33:05)
sh: addr2line: command not found
sh: addr2line: command not found
sh: addr2line: command not found
004  3   ???                                 0x00007fff604c7ff4 0x0 + 140734809014260
005  4   ???                                 0x00007fff604ce58d 0x0 + 140734809040269
006  5   ???                                 0x00007fff604d2432 0x0 + 140734809056306
sh: addr2line: command not found
sh: addr2line: command not found
sh: addr2line: command not found
sh: addr2line: command not found
sh: addr2line: command not found
sh: addr2line: command not found
sh: addr2line: command not found
======= End of  backtrace =======
Abort trap: 6

Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

Attached Files
file #30738:  weechat_crash_20140228_80784.log added by None (757KiB - application/octet-stream - Crash Log)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by dietrich
  • -email is unavailable- added by flashcode (Posted a comment)
  • -email is unavailable- added by None (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 10 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2014-04-09 dietrich Carbon-Copy- Added dietrich
    2014-04-04 flashcode StatusWorks For Me Need Info
        Open/ClosedClosed Open
    2014-03-30 flashcode StatusNeed Info Works For Me
        Open/ClosedOpen Closed
    2014-03-02 flashcode CategoryNone other
        Item GroupNone crash
        StatusNone Need Info
        Assigned toNone flashcode
    2014-02-28 None Attached File- Added weechat_crash_20140228_80784.log, #30738

    Back to the top

    Powered by Savane 3.13-3230.
    Corresponding source code