When executing VPP - built with the option below - I do get a nice
print of all the misaligned memory being accessed.
Among many, I can also see the one causing the SEGFAULT:
/home/mvarlese/repo/vpp/build-
data/../src/vnet/mfib/mfib_entry.c:405:27: runtime error: member access
within misaligned a
Dave & all,
I was suggested by some compiler guys to turn on the gcc option
-fsanitize=undefined since the error (and the actual way I used to fix it)
might be caused by unaligned memory.
I did try that in my local repo and a lot of errors show up for
src/vppinfra/memcpy_sse3.h regarding a "load
Hi Dave,
On Mon, 2017-08-28 at 14:12 -0400, Dave Wallace wrote:
> Marco,
>
>
>
> Thanks for the follow up. Could you please file a Jira for this
> issue
> (https://jira.fd.io/secure/RapidBoard.jspa?rapidView=20&projectKey=VP
> P)
> and/or submit a patch if you find a
Marco,
Thanks for the follow up. Could you please file a Jira for this issue
(https://jira.fd.io/secure/RapidBoard.jspa?rapidView=20&projectKey=VPP)
and/or submit a patch if you find a workaround?
Thanks,
-daw-
On 08/28/2017 12:22 PM, Marco Varlese wrote:
After long digging I managed to fin
After long digging I managed to find the issue...
The problem happens when building VPP using gcc-7 compiler but it
doesn't come up when building it with gcc-6.
I will keep digging into this but I hope it might be of help to you
folks too...
Cheers,
Marco
On Mon, 2017-08-28 at 16:05 +0200, Mar
And a even more complete BT with sources below:
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
vlib_plugin_early_init:356: plugin path /usr/lib64/vpp_plugins
load_one_plugin:184: Loaded plugin: acl_plugin.so (Access Control
Lists)
load_one
Apologies, I forgot to also provide some extra information:
> Using DPDK 17.08.
> A backtrace below:
(gdb) bt
#0 0x7765bced in mfib_entry_create () from
/usr/lib64/libvnet.so.0
#1 0x7765cdc7 in mfib_table_entry_update () from
/usr/lib64/libvnet.so.0
#2 0x77656b85 in ip
Hi,
I'm running the tip of master branch and I get a segmentation fault
when launcing "vpp -c /etc/vpp/startup.conf"
My startup.conf is very simple, I don't even map dpdk interfaces, etc.
since I am using in a virt environment.
I wonder if by any chance a new setting/parameter was introduced whi
