Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#2162 std::bad_alloc

closed-duplicate
nobody
None
Front-end
5
2015-03-20
2013-05-10
Arnost Vecerka
No

The file with code which produced problem is attached.

SDCC -c F_33.c

SDCC : mcs51/gbz80/z80/z180/r2k/r3ka/ds390/pic16/pic14/TININative/ds400/hc08/s08 3.3.0/rc1/ #8592 (May 5 2013) (MINGW32)

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

I apologize for the mistake. I have attached wrong file in the previous report.

1 Attachments

Discussion

  • Maarten Brock
    Maarten Brock
    2013-05-11

    I can reproduce this with both 3.2.0 and 3.3.0rc1.
    It seems this large switch statement is too much for SDCC.
    It's certainly no preprocessor bug.

     
  • Maarten Brock
    Maarten Brock
    2013-12-18

    • Category: Preprocessor --> Front-end
     
  • Ben Shi
    Ben Shi
    2015-03-20

    • status: open --> closed-duplicate
     
  • Ben Shi
    Ben Shi
    2015-03-20

    Duplicate to bug #2062. Since

    1. The similarity of the two test cases (F_33.c in this ticket and foo.c in bug #2062) is 98%.
    2. They produce the same error.