digitalmars.D - Memory allocation failed
- Jason House (2/2) Feb 17 2009 Has anyone else gotten the "Memory allocation failed" exception in D2? I...
- BCS (3/12) Feb 17 2009 One guess (I think I ran across this once) is a single allocation of siz...
- Jason House (4/18) Feb 17 2009 Apparently, setting an array length to -1 will cause this issue. It's
- Walter Bright (2/5) Feb 18 2009 What's wrong with gdb?
- Jason House (3/9) Feb 18 2009 See my issue 2575 in bugzilla. I worked with a gdb developer to diagnose...
- Walter Bright (2/17) Feb 20 2009 thanks
- Jason House (6/24) Feb 22 2009 I see you did post questions to the bugzilla report, and I did provide a...
- Walter Bright (3/29) Feb 24 2009 I think they gave you basically useless information. I'll have to figure...
Has anyone else gotten the "Memory allocation failed" exception in D2? I have to dig deeper to concretely prove it's not my fault, but I do know I wrote my app to avoid memory allocation and watching top showed about 20k of growth over the ~10 minutes it takes to reproduce the bug. I don't look forward to debugging this without gdb. gdb support has been broken in D2 for a while now :(
Feb 17 2009
Reply to Jason,Has anyone else gotten the "Memory allocation failed" exception in D2? I have to dig deeper to concretely prove it's not my fault, but I do know I wrote my app to avoid memory allocation and watching top showed about 20k of growth over the ~10 minutes it takes to reproduce the bug. I don't look forward to debugging this without gdb. gdb support has been broken in D2 for a while now :(One guess (I think I ran across this once) is a single allocation of size<0 as that ends up being GBs
Feb 17 2009
BCS wrote:Reply to Jason,Apparently, setting an array length to -1 will cause this issue. It's unfortunate to not have a stack trace in the error output, or a functional gdb to capture it! I really hope gdb compatiblity will be fixed :(Has anyone else gotten the "Memory allocation failed" exception in D2? I have to dig deeper to concretely prove it's not my fault, but I do know I wrote my app to avoid memory allocation and watching top showed about 20k of growth over the ~10 minutes it takes to reproduce the bug. I don't look forward to debugging this without gdb. gdb support has been broken in D2 for a while now :(One guess (I think I ran across this once) is a single allocation of size<0 as that ends up being GBs
Feb 17 2009
Jason House wrote:Apparently, setting an array length to -1 will cause this issue. It's unfortunate to not have a stack trace in the error output, or a functional gdb to capture it! I really hope gdb compatiblity will be fixed :(What's wrong with gdb?
Feb 18 2009
Walter Bright Wrote:Jason House wrote:See my issue 2575 in bugzilla. I worked with a gdb developer to diagnose the issue immediately prior to submitting the bug report. IIRC, gdb can't determine where the code is because some kind of top level offset is missing. Reading my bug report should be more helpful than my memory.Apparently, setting an array length to -1 will cause this issue. It's unfortunate to not have a stack trace in the error output, or a functional gdb to capture it! I really hope gdb compatiblity will be fixed :(What's wrong with gdb?
Feb 18 2009
Jason House wrote:Walter Bright Wrote:thanksJason House wrote:See my issue 2575 in bugzilla. I worked with a gdb developer to diagnose the issue immediately prior to submitting the bug report. IIRC, gdb can't determine where the code is because some kind of top level offset is missing. Reading my bug report should be more helpful than my memory.Apparently, setting an array length to -1 will cause this issue. It's unfortunate to not have a stack trace in the error output, or a functional gdb to capture it! I really hope gdb compatiblity will be fixed :(What's wrong with gdb?
Feb 20 2009
Walter Bright wrote:Jason House wrote:I see you did post questions to the bugzilla report, and I did provide a response with what details I could deduce without a gdb dev helping me. Do you have enough information to work through the issue? Given how I currently have a program currently behaves differently with or without the -release flag, I'm extra motivated to get gdb working...Walter Bright Wrote:thanksJason House wrote:See my issue 2575 in bugzilla. I worked with a gdb developer to diagnose the issue immediately prior to submitting the bug report. IIRC, gdb can't determine where the code is because some kind of top level offset is missing. Reading my bug report should be more helpful than my memory.Apparently, setting an array length to -1 will cause this issue. It's unfortunate to not have a stack trace in the error output, or a functional gdb to capture it! I really hope gdb compatiblity will be fixed :(What's wrong with gdb?
Feb 22 2009
Walter Bright <newshound1 digitalmars.com> Jason House wrote:Walter Bright wrote:I think they gave you basically useless information. I'll have to figure it out by guesswork.Jason House wrote:I see you did post questions to the bugzilla report, and I did provide a response with what details I could deduce without a gdb dev helping me. Do you have enough information to work through the issue? Given how I currently have a program currently behaves differently with or without the -release flag, I'm extra motivated to get gdb working...Walter Bright Wrote:thanksJason House wrote:See my issue 2575 in bugzilla. I worked with a gdb developer to diagnose the issue immediately prior to submitting the bug report. IIRC, gdb can't determine where the code is because some kind of top level offset is missing. Reading my bug report should be more helpful than my memory.Apparently, setting an array length to -1 will cause this issue. It's unfortunate to not have a stack trace in the error output, or a functional gdb to capture it! I really hope gdb compatiblity will be fixed :(What's wrong with gdb?
Feb 24 2009