[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [GNUnet-developers] segfault caused by gnunet-service-set
From: |
Daniel Golle |
Subject: |
Re: [GNUnet-developers] segfault caused by gnunet-service-set |
Date: |
Mon, 13 Mar 2017 09:04:33 +0100 |
User-agent: |
Mutt/1.8.0 (2017-02-23) |
Hi!
On Mon, Mar 13, 2017 at 02:11:55AM +0100, Christian Grothoff wrote:
> Hi Daniel,
>
> I just pushed a major clean up of the entire set code, which I _hope_
> also fixes this one. Let me know if not...
Looks good and nothing crashed till now (uptime ~ 30 minutes)
Cheers
Daniel
>
> -Christian
>
> On 03/05/2017 10:38 PM, Daniel Golle wrote:
> > Hi!
> >
> > I see this coming up exactly *once* roughly 20 secondes after gnunet
> > was started:
> >
> > gnunet-service-set: segfault at 0 ip b767c7c6 sp bfaae540 error 4 in
> > libgnunetcadetnew.so.6.0.0[b767a000+5000]
> >
> > running gdb on libgnunetcadetnew.so:
> > (gdb) info symbol 0x27c6
> > destroy_port_cb + 47 in section .text
> >
> > So it looks like the *port pointer is no longer valid...
> > Maybe more eyepairs on cadet_api_new.c:1154..1166 are needed to quickly
> > fix this. Maybe it's some mistake in gnunet-service-set...?
> >
> > I don't really have the time to wrap my head around this now, getting
> > tired and facing some busy days... So just wanted to report this in the
> > hope for a quick resolution.
> >
> >
> > Cheers
> >
> >
> > Daniel
> >
> > _______________________________________________
> > GNUnet-developers mailing list
> > address@hidden
> > https://lists.gnu.org/mailman/listinfo/gnunet-developers
> >
>