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.

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

segfault during debug #3875

Closed
rmast opened this issue Jul 18, 2022 · 2 comments
Closed

segfault during debug #3875

rmast opened this issue Jul 18, 2022 · 2 comments

Comments

@rmast
Copy link

rmast commented Jul 18, 2022


Environment

  • Tesseract Version: 5.2.0
  • Commit Number: commit 8c573e4 (HEAD, stweil/main)
  • Platform: Linux Ubuntu20b 5.15.0-1014-azure # 17~20.04.1-Ubuntu SMP Thu Jun 23 20:01:51 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

./configure --enable-graphics --enable-debug -disable-legacy

Current Behavior:

tesseract --dpi 300 -l Latin -c textord_restore_underlines=1 -c textord_show_final_rows=1 -c textord_debug_tabfind=1 -c textord_debug_bugs=1 175789293-f39ddfdb-6f3e-4598-8d16-80a1f4a88b36.jpg outputwithoutinvert3

picture

[ 3098.848254] tesseract[7316]: segfault at 18 ip 00007fda7f267264 sp 00007ffdacd759b0 error 4 in libtesseract.so.5.0.2[7fda7f0ef000+1c5000]
image

Expected Behavior:

No dump

Suggested Fix:

@stweil stweil added the bug label Jul 19, 2022
@stweil
Copy link
Member

stweil commented Jul 19, 2022

The crash occurs because to_win is used but was not created (resulting in this == nullptr).

stweil added a commit that referenced this issue Jul 19, 2022
There still remain memory leaks for the test scenario, but those are less
urgent as they are related to code which is only used for debugging.

Signed-off-by: Stefan Weil <[email protected]>
@stweil
Copy link
Member

stweil commented Jul 19, 2022

I fixed this issue in commit 99d6717.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants