Re: [libmicrohttpd] SEGFAULT after upgrading from 0.9.77 to 1.0.1

[Markus Doppelbauer]

Hi Evgeny,

unsigned int daemon_flags = MHD_USE_INTERNAL_POLLING_THREAD | MHD_USE_POLL | MHD_ALLOW_SUSPEND_RESUME | MHD_USE_ERROR_LOG

Response is generated in a dedicated thread.

I will try to write a testcase.

Best wishes

Am Dienstag, dem 27.02.2024 um 18:19 +0100 schrieb Evgeny Grin:

Hi Markus,

Can you share a larger piece of code or give more details, like used 

mode (internal polling or external polling), polling function, other 

relevant information?

-- 

Evgeny

27-Feb-2024 17:58 (UTC+0100), Markus Doppelbauer via libmicrohttpd wrote:

What was your issue? How did you fix it?

I am getting "Assertion failed" from "connection.c:6864":

   case MHD_CONNECTION_CHUNKED_BODY_UNREADY:

     mhd_assert (0);

This happens if I create a response from callback, e.g.:

     struct MHD_Response *response = MHD_create_response_from_callback( 

MHD_SIZE_UNKNOWN, 32*1024, content_reader_callback, userdata, NULL );

     MHD_add_response_header( response, header.name, header.value );

     statuscode = MHD_queue_response( connection, 200, response );

     MHD_destroy_response( response );

Am Montag, dem 26.02.2024 um 20:51 -0300 schrieb silvioprog:

Problem fixed! \o/

I have a couple of test cases that call some MHD functions internally, 

but after creating fake MHD_Connections to pass to the functions 

instead of NULL the problem was fixed.

Thanks a lot guys!

On Mon, Feb 26, 2024 at 5:41 PM silvioprog <

silvioprog@gmail.com

<mailto:

silvioprog@gmail.com

>> wrote:

Seems like it will be hard to figure out the problem. I mean, since 

the application is crashing, I can understand what is happening. The 

only error message I could catch was this one in the attached picture.

I'll to try to fix the problem or at least reproduce it.

On Mon, Feb 26, 2024 at 4:54 PM silvioprog <

silvioprog@gmail.com

<mailto:

silvioprog@gmail.com

>> wrote:

Hey Christian. =)

Yes sure, I'll try to reproduce the problem and provide all the logs.

On Mon, Feb 26, 2024 at 4:23 PM Christian Grothoff 

<

grothoff@gnunet.org

 <mailto:

grothoff@gnunet.org

>> wrote:

Hi Silvio,

Well, we didn't try to break anything with the update, so you 

shouldn't

have to change anything on your side either. Can you send us a stack

trace/valgrind output and/or test code to reproduce? That'll 

expedite a

fix...

Happy hacking!

-Christian

-- 

Silvio Clécio

-- 

Silvio Clécio