-
Notifications
You must be signed in to change notification settings - Fork 50
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
double free bug in the aspell hash tables #444
Comments
Kevin Atkinson <kevina@sf> commented on 2008-07-30 03:36:50 UTC Logged In: YES I can not seam to reproduce the bug. It will be a big help if you could reproduce the bug with optimization turned off and debugging on i.e. CXXFLAGS="-g". Failing that enabling debugging with optimization may help. |
Giorgos Keramidas <gkeramidas@sf> commented on 2008-07-30 03:44:45 UTC Logged In: YES The original gdbtrace was grabbed from a debugging aspell binary. $ file /usr/local/bin/aspell I'll rebuild without any optimizations, just to make sure I'm not |
Kevin Atkinson <kevina@sf> commented on 2008-07-30 03:50:38 UTC Logged In: YES The stack trace you gave me does not have line numbers, thus I don't think the binary was built with debugging turned on. Also can you do a "locale" and let me see the output. |
Kevin Atkinson <kevina@sf> commented on 2010-03-04 01:28:06 UTC What version of Aspell is this? Use "aspell -v" to find out. |
Kevin Atkinson <kevina@sf> updated the issue on 2010-03-04 01:28:06 UTC
|
I still can't reproduce this, but valgrind did find a bug that was fixed in 3e20784. It not a double-free bug, so I am not sure if it is related. |
Giorgos Keramidas <gkeramidas@sf> created a bug report on 2008-07-30 00:37:53 UTC
(Orig. from https://sourceforge.net/p/aspell/bugs/225)
When spell-checking 'HTH' aspell core dumps in FreeBSD 8.0 with
debugging malloc() options. From a gdb run, it seems that this is a
double-free bug. The memory that aspell is attempting to free when it
aborts is filled with 0x5a and the malloc() manpage of BSD says about
the 'J' debugging flag of malloc():
J Each byte of new memory allocated by malloc(), realloc() or
reallocf() will be initialized to 0xa5. All memory returned by
free(), realloc() or reallocf() will be initialized to 0x5a.
This is intended for debugging and will impact performance nega-
tively.
Here is a terminal script with what I could find so far:
The text was updated successfully, but these errors were encountered: