Programming: Windows Threading Vs Linux Threading (Part 2)

This is in continuation of the previous article 'Windows Threading Vs. Linux Threading', here we'll see a subtle but significant difference in the thread start routine which gets a call from CreateThread() API in the Windows world or pthread_create() function call in the Linux world.

The ThreadProc function in Windows:

DWORD WINAPI ThreadProc(
_In_ LPVOID lpParameter
);

This is an application-defined function that serves as the starting address for a thread.

Note: As per MSDN, Do not declare this callback function with a void return type and cast the function pointer to LPTHREAD_START_ROUTINE when creating the thread.
Code that does this is common, but it can crash on 64-bit Windows.

The return value indicates the success or failure of this function. The return value should never be set to STILL_ACTIVE (259).

In Linux: The function passed as start_routine in the pthread_create() function should correspond to the following C function prototype:
void *threadStartRoutinName(void *);

This is one of the differences we need to take care of while writing thread start routines between Windows and Linux.

Comments

Variadic template class to add numbers recursively during compilation

The idea of having a class to add numbers (variable parameters) during compilation time recursively. Also wanted to restrict types to a single type while sending parameters to class member function. That said, if we mix int, float and double types to add function shall result in compilation error. How do we achieve this. The below is the code which actually helps to achieve this: <code> #include < fmt/format.h > template < typename T> class MyVarSumClass{ private : T _sum = 0 ; public : template < typename ... TRest> T add(T num, TRest... nums){ static_assert (std::conjunction<std::is_same<TRest, T>...>{}); /* Assert fails if types are different */ _sum += num; return add(nums...); // Next parameter packs gets picked recursively } // Base case T add(T num){ _sum += num; return _sum; } }; int main() { My

A simple approach to generate Fibonacci series via multi-threading

T his is a very simple approach taken to generate the Fibonacci series through multithreading. Here instead of a function, used a function object. The code is very simple and self-explanatory. #include <iostream> #include <mutex> #include <thread> class Fib { public: Fib() : _num0(1), _num1(1) {} unsigned long operator()(); private: unsigned long _num0, _num1; std::mutex mu; }; unsigned long Fib::operator()() { mu.lock(); // critical section, exclusive access to the below code by locking the mutex unsigned long temp = _num0; _num0 = _num1; _num1 = temp + _num0; mu.unlock(); return temp; } int main() { Fib f; int i = 0; unsigned long res = 0, res2= 0, res3 = 0; std::cout << "Fibonacci series: "; while (i <= 15) { std::thread t1([&] { res = f(); }); // Capturing result to respective variable via lambda std::thread t2([&] { res2 = f(); }); std::thread t3(

A concept to a product (Kimidori [ 黄緑]) - Part 2

In the previous part , we have seen KIMIDORI [ 黄緑] detect if a URL is malicious. In this part, we will see the details that KIMIDORI [ 黄緑] fetches out of the URL provided. As an example, provided a safe URL, https://www.azuresys.com/, and let's see what it brings out: As we can see, the link is safe and the link is active, which means we can just click on the link to open it on IE. Now it's time to look into the URL report (still under development): We have URLs IP, Location, and HTTP Status code. The Report part is a sliding window, the Show Report button shows as well as hides the report. Show / Hide Report is a toggle button. Let's see if we get the same details for any bad (phishing / malicious) URL: Took an URL example from a phishing link and tested it. The tool detected it as not a good link (Screen Shot Below) & link does not activate unlike a safe URL: Now let's see the report part for more details including domain registration details: It looks like it&

Bits 'n Bytes

Search This Blog