Got GDB dump while turning OFF(or OFF then ON) a plugin

Answered

Permanently deleted user

January 17, 2022 07:37 Edited

Hi,

I am receiving gdb dump caused by 6/ABRT or 11/SEGV while turning OFF (or OFF then ON) a plugin from time to time, and I don't see a plugin .so is mentioned in stack trace. Is there something I should pay attention to throughout the plugin disabling process?

6/ABRT's stack trace:
https://drive.google.com/file/d/1T3PuUAmC77Voke_QkYh4z0ukda14k6A3/view?usp=sharing
https://drive.google.com/file/d/1M9O4fhAKRv3nGrwsQo_jtiXbkdv9ihjg/view?usp=sharing

11/SEGV's stack trace:
https://drive.google.com/file/d/1T6l5kdUSaRbaTdCzJjnE7h3Z7a0a9VrD/view?usp=sharing

0

• 

  Andrey Terentyev

  • Network Optix team

  February 07, 2022 16:04

  Hello James,

  There are no specifics, but the general recommendations.

  Judging by the error codes you got 6/ABRT or 11/SEGV, you've got issues with memory addressing/management/allocation.

  Here are several examples of possible causes.

  - referring not existing pointer
  - out of memory when allocating
  - forgetting to free memory/release pointer after allocation

  Error messages in the files you provided reveals errors related to malloc function.

  malloc is a function of the standard library, stands for memory allocation.

  #2  0x00007f1f72676967 in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f1f727a3b0d "%s\n") at ../sysdeps/posix/libc_fatal.c:181
  #3  0x00007f1f7267d9da in malloc_printerr (str=str@entry=0x7f1f727a5368 "malloc_consolidate(): invalid chunk size") at malloc.c:5342

  This function underlies all the upper level memory management operations.

  You should carefully reconsider what object instances you create/destroy in the constructor/destructor of the Device Agent. 

  0

Please sign in to leave a comment.