-
```
What steps will reproduce the problem?
1.
2.
3.
What is the expected output? What do you see instead?
expected ==> the two lib*.so.
I got errors:
jni/com_googlecode_leptonica_android/stdio/open_m…
-
```
What steps will reproduce the problem?
1. Run two instances of the mate parser in the same JVM
What do you see instead?
Running two instances of the mate parser in the same JVM leads to followin…
-
```
What steps will reproduce the problem?
1. Run two instances of the mate parser in the same JVM
What do you see instead?
Running two instances of the mate parser in the same JVM leads to followin…
-
```
What steps will reproduce the problem?
1. Run two instances of the mate parser in the same JVM
What do you see instead?
Running two instances of the mate parser in the same JVM leads to followin…
-
```
What steps will reproduce the problem?
1. Run two instances of the mate parser in the same JVM
What do you see instead?
Running two instances of the mate parser in the same JVM leads to followin…
-
```
What steps will reproduce the problem?
1. Run two instances of the mate parser in the same JVM
What do you see instead?
Running two instances of the mate parser in the same JVM leads to followin…
-
```
What steps will reproduce the problem?
1. Run two instances of the mate parser in the same JVM
What do you see instead?
Running two instances of the mate parser in the same JVM leads to followin…
-
```
What steps will reproduce the problem?
1. Run two instances of the mate parser in the same JVM
What do you see instead?
Running two instances of the mate parser in the same JVM leads to followin…
-
```
What steps will reproduce the problem?
1. Run two instances of the mate parser in the same JVM
What do you see instead?
Running two instances of the mate parser in the same JVM leads to followin…
-
`kgtk` commands should complain when an output file looks like it will overwrite an input file (except for stdin/stdout). We've had at least one user problem so far due to this gotcha.