[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Packaging Jami progress
From: |
Ricardo Wurmus |
Subject: |
Re: Packaging Jami progress |
Date: |
Fri, 03 Jan 2020 07:35:01 +0100 |
User-agent: |
mu4e 1.2.0; emacs 26.3 |
Jan <address@hidden> writes:
> On Sat, 28 Dec 2019 10:40:09 +0100
> Pierre Neidhardt <address@hidden> wrote:
>
>> This is indeed your problem, I suspect that something broke the
>> wrapper somehow.
>> Can you share your patch set again? I can have a look.
> I didn't really break anything - it works when launching Jami normally
> or using the ring.cx script or the jami-gnome script manually. ring.cx
> starts both the daemon and the client using "jami-gnome", jami-gnome is
> also a script, which exports the path and then starts
> ".jami-gnome-real". Jami works during normal use, but I couldn't debug
> like this, because by passing only ".jami-gnome-real" which is a
> binary, to gdb, the needed path wasn't exported.
You can run “gdb --args /bin/sh /path/to/wrapper” and then "set
follow-fork-mode child" in gdb.
--
Ricardo
- Re: Packaging Jami progress, Jan, 2020/01/01
- Re: Packaging Jami progress, Ricardo Wurmus, 2020/01/03
- Re: Packaging Jami progress, Jan, 2020/01/03
- Re: Packaging Jami progress, Pierre Neidhardt, 2020/01/04
- Re: Packaging Jami progress, Jan, 2020/01/05
- Re: Packaging Jami progress, Jan, 2020/01/06
- Re: Packaging Jami progress, Jack Hill, 2020/01/06
- Re: Packaging Jami progress, zimoun, 2020/01/06
- Re: Packaging Jami progress, Pierre Neidhardt, 2020/01/07
- Re: Packaging Jami progress,
Ricardo Wurmus <=