my project crashes and I don't understand why
-
Hi,
I try to write a simple parser, but function crashes at the end.
I thought to have tracked all mistakes, but obviously I missed some.valgrind tells me:
==197735== by 0x10E942: QString::at(long long) const (qstring.h:1234) ==197735== by 0x10DF06: HtmlStreamReader::readNextElement() (htmlstreamreader.cpp:26)but from my opinion, that line should not fail.
what am I missing?
-
Run your program in a debugger, it will stop where the crash occurs and you can inspect the stacktrace and the local variables at this point.
Regards
-
JFYI: your project runs fine on my setup. No crash, and when running under valgrind, no problems found (some minor memory leaks, but no out of bounds).
I am running debian testing, with Qt 6.8.2. gcc 14.2.0
-
... and the winner is: @aha_1980 - for the most stupid response ever.
debugger crashes at the very beginning, so no chance ...@Diego-Iastrubni
Thank you very much!
Your reply confirmed my suspicion, that it might be a problem related to stacksize or the like.
What ever the real cause was, I was able to find a workaround. Thanks a lot for your attention and time! -
@django-Reinhard said in my project crashes and I don't understand why:
... and the winner is: @aha_1980 - for the most stupid response ever.
debugger crashes at the very beginning, so no chance ...I am glad you have somehow resolved your issue, whatever it was and by whatever means, but @aha_1980's attempt to help and suggestion is not at all "the most stupid response ever", and it's a shame you react to it so impolitely. Running code which "crashes" under a debugger is the first port of call, so often ignored by people posting here, and examining stack/variables can be very useful.
If your debugger "crashes at the very beginning" that itself is worrying.
-
@django-Reinhard said in my project crashes and I don't understand why:
for the most stupid response ever
Please read and follow https://forum.qt.io/topic/113070/qt-code-of-conduct
@aha_1980 , like most other people here, is helping voluntarily and writing such responses is not welcome here. You did not even mention that debugger is crashing in your first post...
