Menu
For a few days, and without changing anything, at least deliberately, in DEBUG CONSOLE in VSCODE I get messages like:
W/.arae_blueprin(14366): Accessing hidden method Lsun/misc/Unsafe;->getInt(Ljava/lang/Object;J)I (greylist, linking, allowed)
W/.arae_blueprin(14366): Accessing hidden method Lsun/misc/Unsafe;->compareAndSwapObject(Ljava/lang/Object;JLjava/lang/Object;Ljava/lang/Object;)Z (greylist, linking, allowed)
W/.arae_blueprin(14366): Accessing hidden method Lsun/misc/Unsafe;->compareAndSwapObject(Ljava/lang/Object;JLjava/lang/Object;Ljava/lang/Object;)Z (greylist, linking, allowed)
W/.arae_blueprin(14366): Accessing hidden method Lsun/misc/Unsafe;->putObject(Ljava/lang/Object;JLjava/lang/Object;)V (greylist, linking, allowed)
D/EGL_emulation(14366): eglMakeCurrent: 0xe1641400: ver 2 0 (tinfo 0xd5f83710)
D/EGL_emulation(14366): eglMakeCurrent: 0xc1f7c2e0: ver 2 0 (tinfo 0xbd495c10)
D/eglCodecCommon(14366): setVertexArrayObject: set vao to 6 (6) 0 0
W/.arae_blueprin(14366): Accessing hidden method Lsun/misc/Unsafe;->getInt(Ljava/lang/Object;J)I (greylist, linking, allowed)
I/DynamiteModule(14366): Considering local module com.google.android.gms.ads.dynamite:0 and remote module com.google.android.gms.ads.dynamite:21200
I/DynamiteModule(14366): Selected remote version of com.google.android.gms.ads.dynamite, version >= 21200
D/eglCodecCommon(14366): setVertexArrayObject: set vao to 4 (4) 0 0
D/eglCodecCommon(14366): setVertexArrayObject: set vao to 0 (0) 1 2
D/eglCodecCommon(14366): setVertexArrayObject: set vao to 0 (0) 1 2
D/eglCodecCommon(14366): setVertexArrayObject: set vao to 4 (4) 1 30
These messages make it difficult for me to read the logs that I send by console.
How can I filter them so they don't appear, or at least filter my own logs?. Thanks.
687
Either choose Reset Location in the context menu or just drag the Debug Console header back into the upper part of the Panel (like to the right or left of the Terminal header).
If you launch your Flutter project from VS Code with F5 / Debug -> Start Debugging then normal debugging functionality (such as breakpoints, stepping, etc.) should just work (as hot-reload will automatically fire on-save).
Show activity on this post. According to this issue it looks like it is not currently possible to filter the debug console in Visual Studio Code, however you could use the filter text field in the logging tab of the Dart DevTools in order to filter the logs that are sent to the console.
Another useful debugging tool is logging. You set logging up programmatically then view the output in the DevTools logging view, or in the console. Flutter was designed with a layered architecture that includes widget, rendering, and painting layers.
VS Code's built-in debugger helps accelerate your edit, compile and debug loop. VS Code has built-in debugging support for the Node.js runtime and can debug JavaScript, TypeScript, or any other language that gets transpiled to JavaScript.
VS Code keeps debugging configuration information in a launch.json file located in a .vscode folder in your workspace (project root folder) or in your user settings or workspace settings. To create a launch.json file, open your project folder in VS Code ( File > Open Folder) and then select the Configure gear icon on the Run view top bar.
According to this issue it looks like it is not currently possible to filter the debug console in Visual Studio Code, however you could use the filter text field in the logging tab of the Dart DevTools in order to filter the logs that are sent to the console. I appreciate that this means that you would need to have the Dart DevTools open in addition to Visual Studio Code, however this would be a useable workaround until such a time as the ability to filter the debug console is implemented in Visual Studio Code.
101
The ability to filter the Debug Console text is coming to v1.49 (see https://github.com/microsoft/vscode-docs/blob/vnext/release-notes/v1_49.md#debug-console-filter):
Debug console now supports filtering. This should make it easier for users to find the output they are looking for in the Debug Console and to be able to hide irrelevant logs. Filter also supports the exclude patterns which should be prefixed with
!. User evaluations are not respecting the filter and are always shown. Like other input boxes in VS Code you can useupanddownarrow to navigate between old filter inputs.
23
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
