On Wed, Jan 31, 2024 at 7:44 PM Simon Walter wrote:
>
> My question about how to debuging should be done. abort() is called on
> apr_initialize():
>
> Program received signal SIGABRT, Aborted.
Does the attached patch fix the issue with apr_initialize()?
Regards;
Yann.
Index:
On 2024-02-01 14:21, Yann Ylavic wrote:
> On Thu, Feb 1, 2024 at 1:56 PM Yann Ylavic wrote:
>>
>> On Wed, Jan 31, 2024 at 7:44 PM Simon Walter wrote:
>>>
>>> Should I use '--enable-pool-debug=yes' or '--enable-pool-debug=verbose'?
>>
>> I'd suggest using simple --enable-pool-debug[=yes] and
On Thu, Feb 1, 2024 at 2:38 PM Simon Walter wrote:
>
> I had partial success with '--enable-pool-debug=yes' and
> '--enable-pool-debug=verbose'. Then I ran into something else regarding
> apr-util. I see there are pre-processor conditions based on APR_POOL_DEBUG.
Yes, you need to both apr and
dev@ team,
I'm wondering if we could/should remove APR_POOL_DEBUG specifics in
apr-util 1.6.x and 1.7.x, otherwise it's not possible run
non-pool-debug apr-util with pool-debug apr.
Fortunately the only dependency on APR_POOL_DEBUG for apr-util seems
to be the apr_bucket code below.
On Thu, Feb
On Wed, Jan 31, 2024 at 7:44 PM Simon Walter wrote:
>
> Should I use '--enable-pool-debug=yes' or '--enable-pool-debug=verbose'?
I'd suggest using simple --enable-pool-debug[=yes] and ASan (Address
Sanitizer, i.e. "-fsanitize=address -fno-sanitize-recover=address" in
$CFLAGS).
Regards,
Yann.
On Thu, Feb 1, 2024 at 1:56 PM Yann Ylavic wrote:
>
> On Wed, Jan 31, 2024 at 7:44 PM Simon Walter wrote:
> >
> > Should I use '--enable-pool-debug=yes' or '--enable-pool-debug=verbose'?
>
> I'd suggest using simple --enable-pool-debug[=yes] and ASan (Address
> Sanitizer, i.e.
On 2024-02-01 14:29, Yann Ylavic wrote:
> On Wed, Jan 31, 2024 at 7:44 PM Simon Walter wrote:
>>
>> My question about how to debuging should be done. abort() is called on
>> apr_initialize():
>>
>> Program received signal SIGABRT, Aborted.
>
> Does the attached patch fix the issue with
