- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Did I mention I hate these kinds of problems?
stack overflow (both 10 and 11 compilers). points to a line in the code that is calling a routine. (it's not my code but a quick perusal shows allocating and later deallocating arrays, etc).
inside the Visual studio environment, both debug and release versions complete normally.
ideas on what i should be looking for?
Linda
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Probably the compiler needs to create a temporary array because it does not know that what you are passing is contiguous. Try turning on Heap Arrays.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Actually, I think it is something else. This rouitne writes out for reports.. 2 of them are written fine. The last two have no content. But perusal of code -- I think I see it.
The routine has an optional argument but instead of looking at "PRESENT" for the argument, he's testing the argument for having characters (LEN_TRIM > 0). I'll change that and I think it will likely fix it.
So the compiler is complaining after it exits the routine....
Linda
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
FYI, though that seems like a problem, that wasn't the problem. Investigating.
Linda
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ah, the proverbial uninitialized variable. A little irritating that I have "Debug everything" on in the debug compile and it doesn't/didn't catch it.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page