Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

SIGABRT mono crash when using gdb to debug on cpp tool version 0.24.0 #3899

Closed
resk8 opened this issue Jul 9, 2019 · 6 comments
Closed

SIGABRT mono crash when using gdb to debug on cpp tool version 0.24.0 #3899

resk8 opened this issue Jul 9, 2019 · 6 comments
Assignees
@pieandcakes
Labels
debugger

Comments

@resk8
Copy link

resk8 commented Jul 9, 2019

After updating cpp tools to 0.24.0, im starting to get this SIGABRT error relate to OpenDebugAd7 i think

here are the logs.
Debug info from gdb:[New LWP 163720]
[New LWP 163721]
[New LWP 163727]
[New LWP 163728]
[New LWP 163729]
[New LWP 163730]warning: File "/nfs/site/disks/are3/dev_tools/vscode-ec/lib/glibc/2.18.90-333.1/lib64/libthread_db-1.0.so" auto-loading has been declined by your auto-load safe-path' set to "$debugdir:$datadir/auto-load". To enable execution of this file add add-auto-load-safe-path /nfs/site/disks/are3/dev_tools/vscode-ec/lib/glibc/2.18.90-333.1/lib64/libthread_db-1.0.so line to your configuration file "/nfs/pdx/home/renatool/.gdbinit". To completely disable this security protection add set auto-load safe-path / line to your configuration file "/nfs/pdx/home/renatool/.gdbinit". For more information about this security protection see the "Auto-loading safe path" section in the GDB manual. E.g., run from the shell: info "(gdb)Auto-loading safe path" warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available.warning: File "/nfs/site/disks/are3/dev_tools/vscode-ec/lib/glibc/2.18.90-333.1/lib64/libthread_db-1.0.so" auto-loading has been declined by your auto-load safe-path' set to "$debugdir:$datadir/auto-load".
warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available.0x00007ffff74bd0bf in pthread_cond_wait@@GLIBC_2.3.2 () from /nfs/site/disks/are3/dev_tools/vscode-ec/lib/glibc/2.18.90-333.1/lib64/libpthread.so.0
Id Target Id Frame

Describe the bug

  • linux suse KDE
  • vscode: 1.32.3:
  • C/C++ Extension Version: 0.24.0

To Reproduce
not sure what to write on reproduce but just launching through launch.json
{
// Use IntelliSense to learn about possible attributes.
// Hover to view descriptions of existing attributes.
// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
"version": "0.2.0",
"configurations": [
{
"name": "(gdb) Launch",
"type": "cppdbg",
"request": "launch",
"program": "${workspaceFolder}/bin",
"args": [
"-ckv",
".."
],
"cwd": "usr/renatool/test/mytest",
"environment":
[
{
"name": "DEBUG",
"value": "1"
}
],
"externalConsole": false,
"MIMode": "gdb",
"setupCommands": [
{
"description": "Enable pretty-printing for gdb",
"text": "-enable-pretty-printing",
"ignoreFailures": true
},
]
}
]
}
@pieandcakes
Copy link
Contributor

@resk8 We didn't change anything around the mono framework that we include in the 0.24.0 update. Can you roll back to 0.23.1 and see if you still run into the problem? Did you also update gdb?

I see this in your log:

 File "/nfs/site/disks/are3/dev_tools/vscode-ec/lib/glibc/2.18.90-333.1/lib64/libthread_db-1.0.so" auto-loading has been declined by your auto-load safe-path' set to "$debugdir:$datadir/auto-load". To enable execution of this file add add-auto-load-safe-path /nfs/site/disks/are3/dev_tools/vscode-ec/lib/glibc/2.18.90-333.1/lib64/libthread_db-1.0.so line to your configuration file "/nfs/pdx/home/renatool/.gdbinit". To completely disable this security protection add set auto-load safe-path / line to your configuration file "/nfs/pdx/home/renatool/.gdbinit". For more information about this security protection see the "Auto-loading safe path" section in the GDB manual. E.g., run from the shell: info "(gdb)Auto-loading safe path" warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available.warning: File "/nfs/site/disks/are3/dev_tools/vscode-ec/lib/glibc/2.18.90-333.1/lib64/libthread_db-1.0.so" auto-loading has been declined by your auto-load safe-path' set to "$debugdir:$datadir/auto-load".
warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available.0x00007ffff74bd0bf in pthread_cond_wait@@GLIBC_2.3.2 () from /nfs/site/disks/are3/dev_tools/vscode-ec/lib/glibc/2.18.90-333.1/lib64/libpthread.so.0

@pieandcakes pieandcakes self-assigned this Jul 10, 2019
@resk8
Copy link
Author

resk8 commented Jul 10, 2019

yeah i rolled back and im having the same issue. so its probably not an issue with the update. There was maintenance update over the weekend that might have changed something on our systems here. I will close the issue then. Do you think that auto-load of the libthread might cause mono to crash?

@resk8 resk8 closed this as completed Jul 10, 2019
@pieandcakes
Copy link
Contributor

@resk8 it sounds like it needs the library to load for mono to work and for some reason the autoload of that library is disabled? I don't know enough about SUSE to tell you why its getting that error.

@resk8
Copy link
Author

resk8 commented Jul 10, 2019

yeah i figured. anyways thanks for the help

@pieandcakes
Copy link
Contributor

is the /nfs/site/disks/are3/dev_tools/vscode-ec/lib/ path part of your app that you are debugging?

@resk8
Copy link
Author

resk8 commented Jul 10, 2019

yeah it kind of is. Our linux Suse system here is missing the gclib (i think or i dont understand) to run the extension so the IT team here have to manually patch the extensions to look for the gclibs that is inside that directory. It worked before but after the maintenance over the weekend probably permissions was changed so i need to investigate here what is going on

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pieandcakes pieandcakes

Labels
debugger
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@resk8 @pieandcakes