Hi all,

I have the same issue. After I built the vpp from sources(master branch)
and run vppctl I see a segmentation fault. This looks to be caused by the
fact that the vlib_mains from init functions of dynamic linked libraries is
0x0.
Following patch will fix the problem:
--- a/src/vlib/global_funcs.h
 19 +++ b/src/vlib/global_funcs.h
 20 @@ -23,7 +23,7 @@ always_inline vlib_main_t *
 21  vlib_get_main (void)
 22  {
 23    vlib_main_t *vm;
 24 -  vm = vlib_mains[os_get_cpu_number ()];
 25 +  vm = vlib_mains ? vlib_mains[os_get_cpu_number ()] :
&vlib_global_main;
 26    ASSERT (vm);
 27    return vm;
 28  }

This is like a part of patch did in commit:
80f54e20270ed0628ee725e3e3c515731a0188f2 need to be reverted.

Is other fix of this issue?

/Adrian

On Tue, Mar 21, 2017 at 4:34 AM, Jon Loeliger <j...@netgate.com> wrote:

> On Mon, Mar 20, 2017 at 9:18 PM, Jon Loeliger <j...@netgate.com> wrote:
>
>> Dave,
>>
>> With the advent of a compiling tree (hooray!), I've updated, rebuilt,
>> installed, and tried running all the C libraries and API pieces again.
>> Sadly, things are not working.
>>
>> Very early in the bring-up of a C executable that is linked to VPP's
>> libraries
>> (vlibmemoryclient vlibapi svm vppinfra), it goes into the weeds trying to
>> load some statically configured CLI initialization functions dynamically:
>>
>>
>
>> 80f54e20270ed0628ee725e3e3c515731a0188f2
>> Author: Dave Barach <d...@barachs.net>
>> Date:   Wed Mar 8 19:08:56 2017 -0500
>>
>>     vlib_mains == 0 special cases be gone
>>
>>     Clean up spurious binary API client link dependency on libvlib.so,
>>     which managed to hide behind vlib_mains == 0 checks reached by
>>     VLIB_xxx_FUNCTION macros.
>>
>>     Change-Id: I5df1f8ab07dca1944250e643ccf06e60a8462325
>>     Signed-off-by: Dave Barach <d...@barachs.net>
>>
>
> Also, if one simply 'git reverts' this one commit on the current top
> of tree, things resume working again.
>
> HTH,
> jdl
>
>
> _______________________________________________
> vpp-dev mailing list
> vpp-dev@lists.fd.io
> https://lists.fd.io/mailman/listinfo/vpp-dev
>
_______________________________________________
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Reply via email to