Summary: | Tilecreator crashes on armel (Maemo) | ||
---|---|---|---|
Product: | [Applications] marble | Reporter: | Dennis Nienhüser <nienhueser> |
Component: | general | Assignee: | marble-bugs |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | bastianholst, justin.zobel, sylvain.pare |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | some future version | ||
Platform: | Compiled Sources | ||
OS: | Other | ||
Latest Commit: | Version Fixed In: |
Description
Dennis Nienhüser
2010-04-03 11:56:26 UTC
Here is a test program: #include <QtCore/QDebug> #include <QtGui/QImage> int main(int argc, char** argv) { if (argc != 2 ) { qDebug() << "Usage: " << argv[0] << " /path/to/image"; return 1; } QImage image(argv[1]); if (!image.isNull()) { qDebug() << "Loaded image " << argv[1] << " with size " << image.width() << "x" << image.height(); } return 0; } Compile with g++ -o test -L /usr/lib/qt4/ -lQtGui test.cpp On Maemo with armel target, it segfaults when passing srtm.jpg (any jpg): ./test ../src/data/maps/earth/srtm/srtm.jpg qemu: uncaught target signal 11 (Segmentation fault) - core dumped but works fine with other image formats (tested png). Works fine in Kubuntu with jpg and png. Can someone with a running Maemo 5 SDK confirm this behavior? Same for me. It crashes in scratchbox, but runs and loads the jpg without a crash on maemo (N900) itself (same jpg). +1 tmp/work/armv7a-oe-linux-gnueabi/marble-1.1.0-r0.0/build/src/tilecreator/tilecreator: cannot execute binary file file tilecreator tilecreator: ELF 32-bit LSB executable, ARM, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.16, not stripped ldd tilecreator not a dynamic executable this result in make failing at 71% and me not being able to build marble for my device. "cannot execute binary file" sounds like a different problem to me. In scratchbox it starts fine, but then segfaults. it is unfortunate Thank you for the report, Dennis. As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |