Is Parrot Sec Supposed to have 3 sys_call_table?

I’m trying to troubleshoot an issue on a Parrot install and I noticed that when I grep the system map for sys_call_table, I get three results. Is that how it is supposed to be?

ffffffff81c002c0 sys_call_table
ffffffff81c01340 ia32_sys_call_table
ffffffff81c02140 x32_sys_call_table

Also, if I try to debug the kernel using gdb, it returns that no debugging symbols are found. Then a warning that core file may not match executable.


Parrot Sec 4.10 burned with dd.

This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.