[cryptopp-users] Re: Strange behavior with -static compilation flag

2023-04-25 Thread Dwight Kulkarni
Further info: *without -static*, this is the output from the remote server: broker got data of size 512 Broker handler thread started... 512 first two bytes are 128 and 198 and 154 *clear text begins with 68 180 -->> this should be 00 02* Either no 00 02 beginning block or no

[cryptopp-users] Re: Strange behavior with -static compilation flag

2023-04-25 Thread Dwight Kulkarni
Hi all: ldd ./server compiled without the -static flag shows following .so dependencies. Since the -static flag will add the same libraries as .a form, it will compile a slightly different version. I am trying to think why the encryption would produce two different results, maybe something li

[cryptopp-users] Re: Strange behavior with -static compilation flag

2023-04-25 Thread Dwight Kulkarni
I got it working by implementing the raw Integer method. See my code below, previous encryption is commented out. I don't know why but it wasn't working otherwise and *I think it has something to do with memory allocation maybe it works with -static flag because some references are staying in s

Re: [cryptopp-users] Re: Strange behavior with -static compilation flag

2023-04-25 Thread Jeffrey Walton
On Tue, Apr 25, 2023 at 7:12 PM Dwight Kulkarni wrote: > > I got it working by implementing the raw Integer method. See my code below, > previous encryption is commented out. I don't know why but it wasn't working > otherwise and I think it has something to do with memory allocation maybe it >

Re: [cryptopp-users] Re: Strange behavior with -static compilation flag

2023-04-26 Thread Dwight Kulkarni
Hi Jeff, I ran address sanitizer: Heap use after free is the problem. I had to use the NEW operator to allocate the ram. What is weird is that usually it will error out right away after it goes out of scope, but this was delayed in recovering the memory, so it was working and then poof the m

Re: [cryptopp-users] Re: Strange behavior with -static compilation flag

2023-04-26 Thread Dwight Kulkarni
Hi Jeff, I ran address sanitizer: Heap use after free is the problem. I had to use the NEW operator to allocate the ram. What is weird is that usually it will error out right away after it goes out of scope, but this was delayed in recovering the memory, so it was working and then poof the m

Re: [cryptopp-users] Re: Strange behavior with -static compilation flag

2023-04-26 Thread Jeffrey Walton
On Wed, Apr 26, 2023 at 6:13 PM Dwight Kulkarni wrote: > > I ran address sanitizer: Heap use after free is the problem. I had to use > the NEW operator to allocate the ram. What is weird is that usually it will > error out right away after it goes out of scope, but this was delayed in > reco

Re: [cryptopp-users] Re: Strange behavior with -static compilation flag

2023-04-26 Thread Jeffrey Walton
On Wed, Apr 26, 2023 at 11:16 PM Jeffrey Walton wrote: > > On Wed, Apr 26, 2023 at 6:13 PM Dwight Kulkarni wrote: > > > > I ran address sanitizer: Heap use after free is the problem. I had to use > > the NEW operator to allocate the ram. What is weird is that usually it > > will error out ri

Re: [cryptopp-users] Re: Strange behavior with -static compilation flag

2023-04-26 Thread Dwight Kulkarni
Hi Jeff, Your code is exactly what I had before. But I was getting that heap error. It only went away when I used NEW. I have never seen that before. I also don't like using NEW at all but it wasn't working. On Wednesday, April 26, 2023 at 11:21:46 PM UTC-4 Jeffrey Walton wrote: > On Wed, Apr

Re: [cryptopp-users] Re: Strange behavior with -static compilation flag

2023-04-26 Thread Jeffrey Walton
On Thu, Apr 27, 2023 at 12:19 AM Dwight Kulkarni wrote: > > Your code is exactly what I had before. But I was getting that heap error. It > only went away when I used NEW. I have never seen that before. I also don't > like using NEW at all but it wasn't working. > When moving an allocation from

Re: [cryptopp-users] Re: Strange behavior with -static compilation flag

2023-04-26 Thread Jeffrey Walton
On Thu, Apr 27, 2023 at 12:19 AM Dwight Kulkarni wrote: > > Your code is exactly what I had before. But I was getting that heap error. It > only went away when I used NEW. I have never seen that before. I also don't > like using NEW at all but it wasn't working. convert_cryptopp_intege and conv

Re: [cryptopp-users] Re: Strange behavior with -static compilation flag

2023-11-02 Thread Catherine Issabel
$500 million dollars available only for good and trusted receiver or mandate Kindly contact the sender for more information:+1 (336) 345-9681 On Thursday, April 27, 2023 at 5:54:52 AM UTC+1 Jeffrey Walton wrote: > On Thu, Apr 27, 2023 at 12:19 AM Dwight Kulkarni > wrote: > > > > Your code is

Re: [cryptopp-users] Re: Strange behavior with -static compilation flag

2023-11-04 Thread Arik Agazarian
We Need wallet address of 7 months for clean transactions, traceable on Blockchain, Ratio 45%/45%/10% Sender/Reciever/Mandate Telegram sender: @Arik_loader On Thu, Nov 2, 2023, 7:28 PM Catherine Issabel wrote: > > $500 million dollars available only for good and trusted receiver or > mandate >