#1390 internal error: Segmentation faul

MinGW (57)
Volker Dirr

Sorry guys for this bad bug report, but it is so nasty.

I compiled this source on different computers:

i can compile it under windows vista, linux, ...

but i also have 2 computers i can't compile the source.
i got a "internal error: Segmentation faul. Please submit full bug report."
in ..\engine\timetableexport.cpp:7019

i don't know how to go on.

it is a windows xp computer with 640 MB ram, but during compiling only 330 mb ram is used.
it use gcc 4.4.0 with qt 4.6. (but i also use that gcc 4.4.0 and qt 4.6 on an other windows vista and it work fine on that computer.)

i got a report from an other guy, that he has similar problems with an windows xp (but on an amd 4200 dual core with 1 gb ram.) he told me that sometimes just modifiing/deleting comments in the source "help". i don't understand that bug. i hope you can give me an hint or we maybe found a stupid bug.


(if file is not longer available, file is already moved to


  • Anonymous - 2010-01-24

    Line 7019 is:

    QString TimetableExport::writeActivitiesRooms(const QList<qint16>& allActivities){

    Sometimes it crashes on other 3 lines: there are another 3 lines similar to this one (6848, 6930 and 7076). In rare cases it compiles, depends on luck.

    Removing the "const" keyword seems to solve the problem. Also, changing "qint16" to "int" solves the problem (this is a hack I made to solve the problem, temporarily).

  • Anonymous - 2010-01-24

    Also, I forgot to say: we are using the MinGW that comes with Qt SDK 4.6.1 or 4.6.0. It is a MinGW with gcc 4.4.0, possibly modified by Qt team.

  • Keith Marshall

    Keith Marshall - 2010-01-25

    Well, the OP said it -- this is a bad bug report. Where is the minimal test case demonstrating that this is anything other than a bug in some other project? Where is the preprocessed source for this test case?

    Other comments point to a defect elsewhere. It isn't the remit of this tracker to follow up on bugs which are not specifically *within* MinGW. For the time being, and until evidence of an actual MinGW bug is forthcoming, I'm marking this "invalid".

  • Keith Marshall

    Keith Marshall - 2010-01-25

    Not a MinGW bug.

    Although your problem may be interesting and causing you problems you wish answers to, it is not a problem with the MinGW runtime,
    w32api, GCC, binutils or msys. Your BUG report has therefore been deleted. If you feel that this needs further discussion then
    please post to mingw-users@lists.sourceforge.net.

    Thanks for your interest in the MinGW Project,
    MinGW Project Administrators

  • Keith Marshall

    Keith Marshall - 2010-01-25
    • status: open --> pending-invalid
  • SourceForge Robot

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 30 days (the time period specified by
    the administrator of this Tracker).

  • SourceForge Robot

    • status: pending-invalid --> closed-invalid

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks