Summary: | crash in a class diagram when selecting an association (or trying to delete it) | ||
---|---|---|---|
Product: | [Applications] umbrello | Reporter: | Pekka Jääskeläinen <pekka.jaaskelainen> |
Component: | general | Assignee: | Umbrello Development Group <umbrello-devel> |
Status: | RESOLVED FIXED | ||
Severity: | crash | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Debian testing | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
test case, try selecting the association, right clicking on it and then clicking on something else, or just pressing del when it's selected
Patch to avoid crashing in this case. |
Description
Pekka Jääskeläinen
2004-09-20 08:34:58 UTC
Created attachment 7589 [details]
test case, try selecting the association, right clicking on it and then clicking on something else, or just pressing del when it's selected
Created attachment 7621 [details]
Patch to avoid crashing in this case.
I don't know the reason for the NULL pointer. The real bug is deeper in the
call chain, this patch just avoids the crash from happening. I have no idea
what the function this crash happens in is supposed to do.
Pekka - Many thanks for the patch. Independently, I made a another change that also stops the crash (see umlview.cpp rev. 1.178) but a detailed analysis is still to be done. Unfortunately your change does not seem to fix the problem completely. It doesn't crash anymore when selecting the association (or even when pressing delete), but when you after selecting the association click on the canvas it still crashes. My patch seems to avoid the crash, but on my home machine I had another instability problem with this test case diagram which I cannot reproduce with this machine at work (at least not anymore after your change), so this might also be an environment dependent crash. On the other hand, I should have almost exactly identical environments (same distro, same compiler) in both computers, only the CPU differs (Athlon vs. P4) which I doubt should make a difference in this case. I can no longer recreate this problem with current CVS. Please reopen this if it still a problem. |