Bug#577393: reproducibly segfaults in uswsusp's s2disk
stanislav.maslovski at gmail.com
Mon Apr 12 10:17:30 UTC 2010
On Mon, Apr 12, 2010 at 09:07:52AM +0200, Simon Josefsson wrote:
> tags 577393 help moreinfo
> Without more information, I think it makes more sense to debug this as a
> s2disk bug than a libgcrypt bug. To really be able to do anything here
> from a libgcrypt point of view, a gdb backtrace is needed, or some
> simpler way to reproduce the problem that doesn't look as potentially
> disk corrupting as s2disk with the above configuration does.
As I wrote, I tried to run s2disk from within gdb, but that freezed my
system. Do you know how can I overcome this?
> Any objection to re-assigning this to s2disk?
No objections, I am not sure myself if this is a s2disk or libgcrypt
bug. Basically, I reported it to libgcrypt because in kernel logs
I saw that the segfault always happens inside libgcrypt's code.
More information about the Pkg-gnutls-maint