| Summary: | Crash when launching kdevelop | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | Favre Ludovic <fludo> |
| Component: | general | Assignee: | KDevelop Developers <kdevelop-devel> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | crash | CC: | claus |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Mandrake RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Favre Ludovic
2004-05-02 14:50:19 UTC
Can you give an english description of what this msg says? Is it that the backtrace is unavailable because of a possible stack corruption? I get the same. It is quite difficult to resolve the problem, but I suspect the following: I use international characters in filenames (upper values of iso8859-7). I have opened a few files containing them in a project. Whenever I try to re-launch that project, these characters cause some QStrings to get corrupted, thus crashing KDevelop. Does yours try to open the last project, which contains latin (say French) characters in filenames? For the traduction: The calling pile ( adress ? ) seem to be unusable. That's probably from the fact that your package was built from a way that block the creation of a correct calling pile, or that the cadre of the pile was seriously damaged in the accident. "It crashed". Useless report. Closing. :) Here is my backtrace. This backtrace appears to be useless. This is probably because your packages are built in a way which prevents creating of proper backtraces, or the stack frame was seriously corrupted in the crash. (no debugging symbols found)...Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread 1103415584 (LWP 3537)] [New Thread 1125051312 (LWP 3582)] [Thread debugging using libthread_db enabled] [New Thread 1103415584 (LWP 3537)] [New Thread 1125051312 (LWP 3582)] [Thread debugging using libthread_db enabled] [New Thread 1103415584 (LWP 3537)] [New Thread 1125051312 (LWP 3582)] (no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...0xffffe410 in ?? () #0 0xffffe410 in ?? () Claus Eksing your backtrace is as useless as the first one. Update to KDevelop 3.1.1 and try again. Claus Eksing your backtrace is useless because your KDevelop binary does not contain any debugging symbols. It was built without debug enabled. You need to download latest KDevelop sources and follow the instructions to build it with debug and then try crashing it. Your backtrace will then be usable. Hope this helps! Hi paragw Thanks I will try that /Claus |