From: SourceForge.net <no...@so...> - 2012-07-17 15:23:55
|
Bugs item #3544361, was opened at 2012-07-15 07:31 Message generated for change (Comment added) made by arve7 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100599&aid=3544361&group_id=599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Arnost Vecerka (arve7) Assigned to: Nobody/Anonymous (nobody) Summary: std::bad_alloc Initial Comment: I have installed new version of SDCC compiler (file sdcc-3.2.0a-setup.exe) and tried to compile program which has two source files. Compilation of the first file terminated with message: This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc Caught signal 22: SIGABRT sdcpp.exe: fatal error: when writing output to : No error Compilation of the second file terminated with similar message: terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. Caught signal 22: SIGABRT Parameters of compilation: -c --std-sdcc99 --opt-code-speed --disable-warning 154 SDCC version 3.0 compiles both source files without problems. Arnost Vecerka ---------------------------------------------------------------------- >Comment By: Arnost Vecerka (arve7) Date: 2012-07-17 08:23 Message: I have uploaded source with one of the functions which caused problems during compilation. Target is MCS51. Arnost Vecerka ---------------------------------------------------------------------- Comment By: Borut Ražem (borutr) Date: 2012-07-16 14:15 Message: Please attach the source file to this bug report. You didn't provide the requested output of compilation with -V option, but I assume that sdcc dies while executing the c++ code. We can't help you if we don't know how to reproduce the problem, that why we need the source file. There is no target specified in "parameters for compilation" (-m option), so it is (the default) mcs51? Borut ---------------------------------------------------------------------- Comment By: Arnost Vecerka (arve7) Date: 2012-07-16 13:47 Message: Operating system: Windows XP Professional SP3 SDCC : mcs51/gbz80/z80/z180/r2k/r3ka/ds390/pic16/pic14/TININative/ds400/hc08/s08 3.2.0 #8008 (Jul 6 2012) (MINGW32) SDCC 3.2.0 gave the same result as 3.2.0a The defect is probably caused by compilation of a long function. I can provide function which makes the defect, but it is not a short one. Arnost Vecerka ---------------------------------------------------------------------- Comment By: Borut Ražem (borutr) Date: 2012-07-15 07:50 Message: Arnost, please provide some more info: - whch Windows version are you using - run sdcc with -V option to see which executable is failing and it's arguments and report the result - a short c source file and the sdcc command line which reproduces the defect Can you please try to compile the same programs with sdcc-3.2.0-setup.exe (not 3.2.0a)? Borut ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100599&aid=3544361&group_id=599 |