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
op/threads.t segfaults with threads and mymalloc #10459
Comments
From perl@profvince.comCreated by perl@profvince.comThe following code, which is a reduced testcase for the op/threads.t failure, segfaults for a perl built with threads and mymalloc enabled : #!perl It also sometimes aborts with this assertion failure : assertion botched (free()ed/realloc()ed-away memory was overwritten?): !(MallocCfg[MallocCfg_filldead] && MallocCfg[MallocCfg_fillcheck]) || !cmp_pat_4bytes((unsigned char*)(p + 1), (((1 << ((bucket) >> 0)) + ((bucket >= 15 * 1) ? 4096 : 0)) - (sizeof(union overhead) + sizeof (unsigned int))) + sizeof (unsigned int), fill_deadbeef) (malloc.c:1546) Valgrind says : ... Perl Info
|
From perl@profvince.comValgrind with more callers : ... |
From @jkeenanOn Tue Jun 22 14:58:31 2010, perl@profvince.com wrote:
[snip Valgrind output; see OP]
This problem appears to still be present in blead. At commit 4b76cb9, I configured as follows: ##### ... which was as close to the OP's configuration as I could understand. I built perl successfully. All tests in t/op/threads.t passed. However, I also tried a script based on the OP's script; see attached. At 1000 repetitions, the program completed successfully. However at 5000 reps I got a seg fault and at 10000 I got something like the weird results the OP posted. ##### Thank you very much. |
From @jkeenan |
The RT System itself - Status changed from 'new' to 'open' |
From @jkeenanOn Wed Dec 11 19:05:02 2013, jkeenan wrote:
I next configured the same way except omitting the '-mymalloc': ##### This time, my test script completed successfully at each of 1000, 5000, and 10000 reps. (The 10,000 rep case took 2:48 to run on dromedary.) So '-Dmymalloc' appears to be the most problematic argument. Thank you very much. |
From @jkeenanOn Thu, 12 Dec 2013 03:18:20 GMT, jkeenan wrote:
Should have typed: "except omitting the '-Dusemymalloc':"
Should have typed: "So '-Dusemymalloc' appears to be the most problematic argument."
-- |
Migrated from rt.perl.org#75972 (status was 'open')
Searchable as RT75972$
The text was updated successfully, but these errors were encountered: