On 03/24/2016 12:31 AM, john hood wrote:
> I haven't been able to chase these glibc details down. Do you have
> pointers to specifics for this?
My assessment was based just on reading the referenced glibc-help
thread, and the commit it referenced --
https://sourceware.org/git/gitweb.cgi?p=glibc.gi
On 3/22/16 9:48 PM, Matthew Gabeler-Lee wrote:
> On Tue, 22 Mar 2016 23:21:31 +0100 Goffredo Baroncelli
> wrote:
>> Please give a look to
>>
>> https://sourceware.org/ml/libc-help/2016-03/msg00010.html
>>
>> to me it seems that the real problem is in glibc.
>
> From reading that thread and lookin
According to Florian Weimer [1] I filed a bug against glibc:
https://sourceware.org/bugzilla/show_bug.cgi?id=19861
[1] https://sourceware.org/ml/libc-help/2016-03/msg00012.html
BR
G.Baroncelli
--
gpg @keyserver.linux.it: Goffredo Baroncelli
Key fingerprint BBF5 1610 0B64 DAC6 5F7D 17B2 0EDA
On Tue, 22 Mar 2016 21:48:43 -0400 Matthew Gabeler-Lee
wrote:
[...]
> But what we have here is an uncommon case driven by mosh's linker
> options, which means that the glibc workaround for protobuf's incorrect
> linker options doesn't (can't?) work.
Why are you stating that passing "-lpthread" i
On Tue, 22 Mar 2016 21:48:43 -0400 Matthew Gabeler-Lee
wrote:
[...]
> But what we have here is an uncommon case driven by mosh's linker
> options, which means that the glibc workaround for protobuf's incorrect
> linker options doesn't (can't?) work.
Why are you stating that passing "-lpthread" i
On Tue, 22 Mar 2016 23:21:31 +0100 Goffredo Baroncelli
wrote:
> Please give a look to
>
> https://sourceware.org/ml/libc-help/2016-03/msg00010.html
>
> to me it seems that the real problem is in glibc.
>From reading that thread and looking at the referenced git commit, I'm
not convinced it's a gl
On Mon, 21 Mar 2016 19:23:54 -0400 Matthew Gabeler-Lee
wrote:
> Package: mosh
> Version: 1.2.5-1.1
> Followup-For: Bug #817929
>
> Looks like upstream has a patch for this:
>
> https://github.com/mobile-shell/mosh/pull/732/commits/a47917b97606a03f6bbf0cafd1fcd495b0229790
Package: mosh
Version: 1.2.5-1.1
Followup-For: Bug #817929
Looks like upstream has a patch for this:
https://github.com/mobile-shell/mosh/pull/732/commits/a47917b97606a03f6bbf0cafd1fcd495b0229790
Though it looks like that's a hack and they really want this fixed in
protobuf:
https://githu
Ok, I was able to track down a __very__ minimal test case: the problem seems to
be a "strange" interaction between the linker flag used during the creation of
libutemper, and the inclusion of -lpthread[*] during the linking of mosh-server.
It is not a problem related to mosh and/or libutempter. I
Thanks for the clues here.
I'm working on the issue from the Mosh side, see:
https://github.com/mobile-shell/mosh/issues/727
I am not sure that libutempter0 is the real culprit, however I find a very
strange behavior:
If I preload libutempter mosh-server didn't crashes. Instead if I run
mosh-server alone, it crashes:
$ ldd /usr/bin/mosh-server
linux-vdso.so.1 (0x7ffce553b000)
libtinfo.so.5 => /l
(can't see my previous message. resending.)
#0 0x in ?? ()
#1 0xb7be786c in execute_helper (master_fd=master_fd@entry=5,
argv=argv@entry=0xbfffebbc) at iface.c:110
#2 0xb7be79d3 in utempter_add_record (master_fd=5, hostname=0xb28c
"mosh [3749]") at iface.c:146
#3 0x80006d59 in run_s
It seems that the problem is related to libutempter0. If commenting the call
in the source of mosh-server, the problem disappear...
I have the same problem. I found that in dmesg, there were several lines
about mosh-server crashing by segfault, for example:
[ 2980.423340] mosh-server[7104]: segfault at 0 ip (null) sp bfd4bb6c error
14 in mosh-server[80001000+58000]
Here's some info from running mosh-server in GDB. I don't hav
Package: mosh
Version: 1.2.5-1.1
Followup-For: Bug #817929
I can confirm that. After a recent update (but I was sure which one) mosh stops
to work.
The problem seems to be in mosh-server which ends with a SIGSEGV after it forks:
$ strace -f mosh-server
execve("/usr/bin/mosh-server&quo
Package: mosh
Version: 1.2.5-1.1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Mosh is unable to connect to debian sid's mosh-server currently. I have
two instances of debian sid, a laptop and a VPS. Neither can connect to
each other with mosh, or even them selfs with
16 matches
Mail list logo
