Comment 5 for bug 45930

Nothing in here points to glibc so far. Most of the time when glibc is at the end of the stack trace, it's because bad data has been handed in. You might try ltrace to see what glibc was called with. As always, the trick is getting a decent reduced testcase.

I also beleive that the final Dapper kernel has been uploaded already, so you're unlikely to see that fixed until Edgy opens up.