>
> This appears to be a bug in DBX.
>

The main problem is not with the backslash. The main problem is memcpy from 
NULL address:

RSA validation suite running...


signal SEGV (no mapping at the fault address) in _memcpy at 
0xffffffff7e200678
0xffffffff7e200678: _memcpy+0x0044:     ldx      [%o1 + %o0], %o3
Current function is CryptoPP::CopyWords
   28                   memcpy(r, a, n*WORD_SIZE);^M
(dbx) print r
...
(dbx) print a
a = (nil)

This NULL address comes from some field m_n:

Current function is CryptoPP::RSAFunction::PreimageBound
   47           Integer PreimageBound() const {return m_n;}^M
(dbx) print m_n
dbx: internal error: /home/abuild/agorev/cryptopp/cryptopp-master.2/misc.h:
51: bad token '\'

dbx: warning: Errors encountered while skimming "rsa.cpp" for macro 
definitions.
             See `help macro skimming-errors' for more explanation.

m_n = {
   reg  = {
       m_alloc = {
/* try using "print -r" to see any inherited members */
       }
       m_mark  = 1025U
       m_size  = 0
       m_ptr   = (nil)
   }
   sign = POSITIVE
}
(dbx)

But I don't know yet why it is so.

> Nothing is jumping out at me for the RSA gear. For completeness, did you 
> perform a 'make distclean' to ensure everything got rebuilt using the same 
> compiler flags?


Yes, kind of. After changing CMakeLists.txt I just removed all Makefiles 
and then regenerated them again (see attached log in my previous email):

$ vim ../CMakeLists.txt
$ rm -rf ./*
$ cmake -DCMAKE_BUILD_TYPE=Debug ..

As I understand technically it is a build from scratch.


I think that change casts a wider net than needed. -xmemalign=4i should be 
> limited to SPARC64, and maybe SPARC. It should not apply to the Intel 
> machines. Applying it to Intel machines will cause a warning.

...

> Yeah, we may as well back out the former change, and go with the 
> -xmemalign=4i. A new PR will be fine.
>

Ok. Will try to separate them, and will make PR. 

-- 
-- 
You received this message because you are subscribed to the "Crypto++ Users" 
Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscr...@googlegroups.com.
More information about Crypto++ and this group is available at 
http://www.cryptopp.com.
--- 
You received this message because you are subscribed to the Google Groups 
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cryptopp-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to