Oh, in fact the second trace is also in animWalkNext(), however, the
stack trace is missing an address for it:
#0 animWalkNext (w=0x8710850) at animation.c:3252
it should be
#0 0xb58694e8 in animWalkNext (w=0x81eda10) at animation.c:3048
Smells like a gdb buglet. I don't know how common this kind of glitch
is, but I guess I can cater for that in apport.
** Changed in: apport (Ubuntu)
Status: Invalid => Triaged
--
stacktrace comparisons
https://bugs.launchpad.net/bugs/269133
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
