Subject: Re: [libssh2] #186: libssh gets stuck at kex_method_diffie_hellman_groupGP_sha1_key_exchange. CPU utilization goes upto 100%

Re: [libssh2] #186: libssh gets stuck at kex_method_diffie_hellman_groupGP_sha1_key_exchange. CPU utilization goes upto 100%

From: libssh2 Trac <trac_at_libssh2.stuge.se>
Date: Mon, 13 Dec 2010 07:02:06 -0000

#186: libssh gets stuck at kex_method_diffie_hellman_groupGP_sha1_key_exchange.
CPU utilization goes upto 100%
---------------------------------------------------------------------------------------+
  Reporter: www.google.com/accounts/o8/id?id=aitoawlhggg_yplkl7grwwpbbum-omtqud4rmna | Owner: bagder
      Type: defect | Status: assigned
  Priority: normal | Milestone: 1.2.8
 Component: crypto | Version: 1.2.2
Resolution: | Keywords:
    Blocks: | Blocked By:
---------------------------------------------------------------------------------------+

Comment (by stuge):

 Replying to [comment:3 www.google.com/accounts/o8/id?id
 =aitoawlhggg_yplkl7grwwpbbum-omtqud4rmna]:
> It gets stuck in the gcrypt's , gcry_mpi_copy () function, with the cpu
 utilization going to 100% and staying that way till we terminate the
 process.

 Are you positive that it is really stuck inside the libgcrypt function,
 and that the problem is not that the function is called over and over?

 Can you work with gdb when it gets stuck? Step through? What does it
 actually do in that function? Also, it would be helpful to build a
 libgcrypt which includes debugging symbols.

 If it really does get stuck inside libgcrypt then maybe the problem isn't
 actually with libssh2. (Though it could also be a problem in libssh2 that
 gives libgcrypt bogus data and causes it to run off and do something
 silly.)

-- 
Ticket URL: <http://trac.libssh2.org/ticket/186#comment:4>
libssh2 <http://trac.libssh2.org/>
C library for writing portable SSH2 clients
_______________________________________________
libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
Received on 2010-12-13