Stackoverflow error when using plantuml gui - plantuml

I have been using Plantuml gui using the following command.
java -jar plantuml.jar -gui
It worked fine for a while but then suddenly I started getting the following error. Everything has slowed down and diagram images are no longer being generated, the GUI does not list the image files in the folder I have selected. Any help will be much appreciated.
Exception in thread "AWT-EventQueue-0" java.lang.StackOverflowError
at java.io.InputStream.<init>(Unknown Source)
at java.io.FileInputStream.<init>(Unknown Source)
at net.sourceforge.plantuml.AFileRegular.open(AFileRegular.java:57)
at net.sourceforge.plantuml.preproc.FileWithSuffix.getReader(FileWithSuffix.java:65)
at net.sourceforge.plantuml.preproc.StartDiagramExtractReader.getReadLine(StartDiagramExtractReader.java:106)
at net.sourceforge.plantuml.preproc.StartDiagramExtractReader.containsStartDiagram(StartDiagramExtractReader.java:136
)
at net.sourceforge.plantuml.preproc2.PreprocessorInclude3.getReaderInclude(PreprocessorInclude3.java:326)
at net.sourceforge.plantuml.preproc2.PreprocessorInclude3.manageFileInclude(PreprocessorInclude3.java:262)
at net.sourceforge.plantuml.preproc2.PreprocessorInclude3.access$500(PreprocessorInclude3.java:75)
at net.sourceforge.plantuml.preproc2.PreprocessorInclude3$Inner.readLineInternal(PreprocessorInclude3.java:149)
at net.sourceforge.plantuml.preproc2.ReadLineInsertable.readLine(ReadLineInsertable.java:65)
at net.sourceforge.plantuml.preproc2.Preprocessor2.readLine(Preprocessor2.java:87)

I have found the problem. The StackOverflowError should have given me an hint, but I missed it. Usually it is related to a recursive loop.
I am using the file include feature and had a circular file reference. So plantuml was going (or rather I was sending it) into an infinite loop and therefore it was running out of stack space.

Related

Incorrect reference DLL in Assembly Microsoft.Extensions.DependencyInjection, Version 3.1.2.0

I am stuck at a strange issue in EntityFrameworkCore 3.1.2:
That is my application logging an error Further to my checks with .NET Reflector, I see that the assembly Microsoft.Extensions.DependencyInjection, Version 3.1.2.0 indeed references 3.1.0.0 of Microsoft.Extensions.DependencyInjection.Abstractions:
My application is targetted to net48.
I tried to narrow down the issue by writing a simple application, and it still gives the same error. Any help is much appreciated!
Edit: I figured out that the issue was caused by the fact that I have code in place to create an AppDomain and the faulting code was being executed inside that. I still don't know what is causing it. My assumption is the references should still work correctly inside a cusotm AppDomain.

Locating kernel properties in Linux via C driver

so I'm doing research for my thesis but I've run into an issue. I'm using a driver my mentor has given me to analyze memory and extract features from a running process. The driver is written in C and I'm running it in Ubuntu 16.04 and the error I'm having is when I compile. My current kernel version is 4.10.0-42-generic.
The following are the three lines are giving an error because they are not found.
(*task->active_mm).page_table_lock.rlock.raw_lock.tickets.head
(*task->active_mm).shared_vm
task->alloc_lock.rlock.raw_lock.tickets.head
For the first, the error starts on tickets I think. For the second shared_vm isn't found and for the last tickets is also where the error begins. My understanding is that the properties are no found.
I've been going through the kernel source files via https://elixir.free-electrons.com/linux/latest/source/kernel in the hopes of locating these properties but if anyone knows where they are or can help me locate them that would be very helpful. I'm new to all this so again any help is really appreciated.
Edit: The specific errors are: has no member named 'tickets', has no member named shared_vm, and has no member named 'tickets' for each respective line of code. Unfortunately I can't share any more code due to my professors request. Screenshot of when I try to 'make'

Bad Image Format Exception when creating record in database

I'm using Entity Framework(model first) in my C# project ,and i am using SQL Server as database.When i'm trying to add a record in a table i encounter this exception.
What's the problem?
Your error is unrelated to that line. If you view the documentation for that exception, it says:
The exception that is thrown when the file image of a dynamic link library (DLL) or an executable program is invalid.
Together with the message, "Bad IL range," I would think you have a corrupted assembly somewhere.
Possible solutions
Look at the exception details to determine which file for which the exception was thrown
If it's a file built by your project, try to clean solution and rebuild
If it's a library, reinstall it
Check if you have anything processing your assemblies, like an obfuscator -- see this post
Last resort: check for viruses, hardware issues, and reinstall .NET

theme.res file does not open anymore, codename one themes

Themes.res file is not opening.
What do i do ?
However, the app is working.
The exception that I am getting on the console while opening the file is:
java.lang.NullPointerException
at com.codename1.ui.util.Resources.createImage(Resources.java:936)
at com.codename1.ui.util.EditableResources.createImage(EditableResources.java:2332)
at com.codename1.ui.util.Resources.loadFont(Resources.java:1119)
at com.codename1.ui.util.EditableResources.loadFont(EditableResources.java:1932)
at com.codename1.ui.util.EditableResources.openFileWithXMLSupport(EditableResources.java:426)
at com.codename1.designer.ResourceEditorView$LoadResourceFileAction.exectute(ResourceEditorView.java:4112)
at com.codename1.ui.resource.util.BlockingAction.run(BlockingAction.java:88)
at java.lang.Thread.run(Unknown Source)
Is there any way I can recover this file / data ?
First verify that the file isn't a 0 size file, if it got corrupted to that level you will need to restore from backup. This hasn't happened for us in years as far as I know but its always a risk.
Next make sure you didn't remove/rename any ttf fonts that might be used by the theme, this is a common cause for failures in the designer.
Next we need to see the actual error and to do that we need to run the designer from command line using:
java -jar ~/.codenameone/designer_1.jar
(code for Mac/Linux replace ~ with your home directory and reverse the slashes for Windows).
Now try to open the resource file and see if you get an exception in the console. Assuming you do we will know more about it and might be able to help you recover your data.
We are currently migrating to new XML based format which should become the default soon.

Obfuscation causes VerifyError: Expecting a stackmap frame

We are using latest JDK 7 (u45) and ProGuard Version 4.10
Lately starting our distribution fails, after obfuscating it, with the following error:
Exception in thread "main" java.lang.VerifyError: Expecting a stackmap frame at
branch target 155
Exception Details:
Location:
com/bla/bla/service/ioc/SpringBootstrap.c()V #0: getstatic
Reason:
Expected stackmap frame at this location.
Bytecode:
0000000: b200 73b6 008b 9900 82b2 0073 b800 933b
0000010: 1a99 0074 b200 73b6 008d 9900 6bb2 0074
0000020: 1221 b600 cfb8 0092 4c2b b600 9c12 1db9
...
Exception Handler Table:
bci [0, 152] => handler: 155
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Unknown Source)
at java.lang.Class.getMethod0(Unknown Source)
at java.lang.Class.getMethod(Unknown Source)
at sun.launcher.LauncherHelper.getMainMethod(Unknown Source)
at sun.launcher.LauncherHelper.checkAndLoadMain(Unknown Source)
I found several discussions about this topic on StackOverflow, like
java-lang-verifyerror-expecting-a-stackmap-frame-at-branch-target-jdk-1-7
java-lang-verifyerror-expecting-a-stackmap-frame
understanding-how-to-resolve-inconsistent-stackmap-frames-exception
java-7-inconsistent-stackmap-frames-need-help-understanding-why-solution-wor
From what I understood is, that java 7 uses a stricter verification and introduced a stack map for classes to verify the code. So somehow during my obfuscation process this map seems to get corrupted, since only this exception occurs, when I obfuscate my project with proguard.
Disabling the verification with -XX:-UseSplitVerifier and starting the builded jar helps, but im not really sure if that should be the way handling this issue.
So I wonder if anyone else had a simular error? Or if anyone might even knows a specific way to solve this, for example by adjusting the proguard konfiguration for the obfuscation process?
I assume you are not specifying -dontpreverify? That option will almost certainly lead to these errors, since it will stop ProGuard from updating the StackMapTable attribute. The attribute was optional in Java 6, but it is required in Java 7.
You could still try a beta version of ProGuard 4.11, but it is unlikely that it makes a difference here. If you mail me the processed class file, I'll look into it.
(I am the developer of ProGuard)
In case you guys didn't find a solution yet, you may try to check if you have -microedition option. Here's why it related to StackMap. Removing this option fixed this issue for me.
I also faced the same challenge when migrating my application from 1.6 to 1.7. After huge struggle, we found a fix to address the issue.
Approach 1: Either you can use -XX:-UseSplitVerifier argument will resolve this issue and you don't need to worry about to upgrade the library files.
Approach 2: I have followed the below steps to overcome the issue. Step 1: Identify and keep a list of external libraries consumed by your application. Step 2: Once you identify the list, keep removing one by one external library files and plug in upgraded version library files which will help you to isolate the library which might causing the issue. In my case: j2ee.jar and openjpa-1.2.2 jar files created an issue and then I have upgraded these libraries which had resolved the migration issues.
Hence, It is bit of slow and painful process to figure out which library causing the issue and arrest it.
I hope, this information might be useful because it is based out of my real time experience.

Resources