Thank you very much for your fast & extensive response! In fact I'm still stucked on debian oldstable (2.6.32) which explains the build issue. And the SIGSEV occurs only in a specific border use-case.
Anyway - I opened GitHub issues #1475, #1476, #1477 to track those. Thanks for your great work! - Ben Am 23.05.2014 19:59, schrieb ridiculous_fish - corydo...@ridiculousfish.com: > Hi, sorry to hear about your issues. > > Please open a github issue for your segfaults at > http://github.com/fish-shell/fish-shell/issues with any information you have, > including your environment (OS version). Steps to reproduce are especially > appreciated. It goes without saying that segfaults are very serious. > > Very recently there was a large merge into trunk, to support running without > fishd. This explains the recent build instability. Are you running a > pre-2.6.36 Linux kernel? Anyways expect that to be fixed in the next few > hours. > > Regarding warnings: what is your build environment? A build of ToT for me > produces only two (harmless) warnings on g++ 4.6, and none with clang. > > zanchey can give an update on the security fix. > > Thanks, > _fish > > On May 23, 2014, at 2:29 AM, fishmailing.jexp...@recursor.net wrote: > >> Since a few weeks, I do have a few, new issues with fish: >> >> 1) I do experience a lot more segafaults in fish all at the same address >> (git 023af55). See below: >> >> System Events >> =-=-=-=-=-=-= >> May 23 10:07:41 srv kernel: [553082.845359] fish[29854]: segfault at >> 6300000061 ip 0000006300000061 sp 00007f24826857e8 error 14 >> May 23 10:17:56 srv sshd[29989]: error: bind: Address already in use >> May 23 10:17:56 srv sshd[29989]: error: channel_setup_fwd_listener: >> cannot listen to port: 63364 >> May 23 10:17:56 srv kernel: [553697.846297] fish[29980]: segfault at >> 6300000061 ip 0000006300000061 sp 00007f3b155417e8 error 14 >> May 23 10:18:59 srv kernel: [553761.303091] fish[27923]: segfault at >> 6300000061 ip 0000006300000061 sp 00007fff14eab028 error 14 >> May 23 10:18:59 srv kernel: [553761.303105] fish[30050]: segfault at >> 6300000061 ip 0000006300000061 sp 00007f76c80c47e8 error 14 >> May 23 10:18:59 srv kernel: [553761.303105] >> May 23 10:28:11 srv kernel: [554312.863817] fish[30154]: segfault at >> 6300000061 ip 0000006300000061 sp 00007f32d476c7e8 error 14 >> >> My logins on that server are mostly remote via ssh and port-forwarding >> >> 2) On following the fish HEAD, the build started to complain with quite a >> few warnings over the past weeks. The current head (451c97f) doesn't build >> for me at all. >> >> env_universal_common.cpp: In member function ‘void >> universal_notifier_inotify_t::reestablish_watch()’: >> env_universal_common.cpp:1641: error: ‘IN_EXCL_UNLINK’ was not >> declared in this scope >> >> So how can I help to solve those segfault? >> And what's about those warning / code quality issues. Is there some major >> refactoring in progress? >> And which version includes the security fix (or is it still under >> development?) >> >> Thanks >> - Ben ------------------------------------------------------------------------------ The best possible search technologies are now affordable for all companies. Download your FREE open source Enterprise Search Engine today! Our experts will assist you in its installation for $59/mo, no commitment. Test it for FREE on our Cloud platform anytime! http://pubads.g.doubleclick.net/gampad/clk?id=145328191&iu=/4140/ostg.clktrk _______________________________________________ Fish-users mailing list Fish-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fish-users
