October 2017 - mod_cluster-issues

[JBoss JIRA] (MODCLUSTER-627) Move https://ci.modcluster.io/ job bodies to https://github.com/modcluster/ci.modcluster.io

by Michal Karm Babacek (JIRA)

Michal Karm Babacek created MODCLUSTER-627: ---------------------------------------------- Summary: Move https://ci.modcluster.io/ job bodies to https://github.com/modcluster/ci.modcluster.io Key: MODCLUSTER-627 URL: https://issues.jboss.org/browse/MODCLUSTER-627 Project: mod_cluster Issue Type: Bug Components: CI & Packaging Reporter: Michal Karm Babacek Assignee: Michal Karm Babacek We don't want to keep the build scripts in the Jenkins job bodies. Let's move them to git. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-603) https://ci.modcluster.io windows httpd: mod_proxy_cluster for Apache Lounge

by Michal Karm Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-603?page=com.atlassian.jira.pl... ] Michal Karm Babacek resolved MODCLUSTER-603. -------------------------------------------- Resolution: Done > https://ci.modcluster.io windows httpd: mod_proxy_cluster for Apache Lounge > --------------------------------------------------------------------------- > > Key: MODCLUSTER-603 > URL: https://issues.jboss.org/browse/MODCLUSTER-603 > Project: mod_cluster > Issue Type: Bug > Components: CI & Packaging > Reporter: Michal Karm Babacek > Assignee: Michal Karm Babacek > > mod_proxy_cluster regular CI for users of http://apachelounge.com/ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-626) Automatically allocated function local variable address overwrites function parameter

by Michal Karm Babacek (JIRA)

Michal Karm Babacek created MODCLUSTER-626: ---------------------------------------------- Summary: Automatically allocated function local variable address overwrites function parameter Key: MODCLUSTER-626 URL: https://issues.jboss.org/browse/MODCLUSTER-626 Project: mod_cluster Issue Type: Bug Components: Native (httpd modules) Affects Versions: 1.3.7.Final, 2.0.0.Alpha1 Environment: C99 (apparently both GNU and MSVC) Reporter: Michal Karm Babacek Assignee: George Zaronikas Fix For: 2.0.0.Alpha1 I went through the cppcheck static analysis report on the current mod_proxy_cluster code base, see [cppcheck.log|https://ci.modcluster.io/job/mod_proxy_cluster-2.x-windows/DISTRO=apache-lounge,label=w2k12r2/93/artifact/cppcheck.log/*view*/], and among *many* warnings and style check failures, there was a one outstanding error reported, which set me wondering. The error occurs on two places and I'm scratching my head as to whether is is a false positive or not, WDYT? * [native/mod_manager/domain.c:198|https://github.com/modcluster/mod_proxy_c...]: (error) Address of local auto-variable assigned to a function parameter. * [native/mod_manager/node.c:227|https://github.com/modcluster/mod_proxy_clu...]: (error) Address of local auto-variable assigned to a function parameter. Is it O.K. to handle local, function scope, automatically allocated variable this way? To use it's address later in ap_slotmem_do? Couldn't it trigger undefined behaviour and cause some of our rare, hard to reproduce crashes? Feel free to pick up any other pertinent messages from the log. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-625) Automatically allocated function local variable address overwrires function parameter

by Michal Karm Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-625?page=com.atlassian.jira.pl... ] Michal Karm Babacek updated MODCLUSTER-625: ------------------------------------------- Affects Version/s: 1.3.7.Final 2.0.0.Alpha1 > Automatically allocated function local variable address overwrires function parameter > ------------------------------------------------------------------------------------- > > Key: MODCLUSTER-625 > URL: https://issues.jboss.org/browse/MODCLUSTER-625 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.3.7.Final, 2.0.0.Alpha1 > Environment: C99 (apparently both GNU and MSVC) > Reporter: Michal Karm Babacek > Assignee: George Zaronikas > Fix For: 2.0.0.Alpha1 > > > I went through the cppcheck static analysis report on the current mod_proxy_cluster code base, see [cppcheck.log|https://ci.modcluster.io/job/mod_proxy_cluster-2.x-windows/DISTRO=apache-lounge,label=w2k12r2/93/artifact/cppcheck.log/*view*/], and among *many* warnings and style check failures, there was a one outstanding error reported, which set me wondering. > The error occurs on two places and I'm scratching my head as to whether is is a false positive or not, WDYT? > * [native/mod_manager/domain.c:198|https://github.com/modcluster/mod_proxy_c...]: (error) Address of local auto-variable assigned to a function parameter. > * [native/mod_manager/node.c:227|https://github.com/modcluster/mod_proxy_clu...]: (error) Address of local auto-variable assigned to a function parameter. > Is it O.K. to handle local, function scope, automatically allocated variable this way? To use it's address later in ap_slotmem_do? Couldn't it trigger undefined behaviour and cause some of our rare, hard to reproduce crashes? > Feel free to pick up any other pertinent messages from the log. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-625) Automatically allocated function local variable address overwrites function parameter

by Michal Karm Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-625?page=com.atlassian.jira.pl... ] Michal Karm Babacek updated MODCLUSTER-625: ------------------------------------------- Summary: Automatically allocated function local variable address overwrites function parameter (was: Automatically allocated function local variable address overwrires function parameter) > Automatically allocated function local variable address overwrites function parameter > ------------------------------------------------------------------------------------- > > Key: MODCLUSTER-625 > URL: https://issues.jboss.org/browse/MODCLUSTER-625 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.3.7.Final, 2.0.0.Alpha1 > Environment: C99 (apparently both GNU and MSVC) > Reporter: Michal Karm Babacek > Assignee: George Zaronikas > Fix For: 2.0.0.Alpha1 > > > I went through the cppcheck static analysis report on the current mod_proxy_cluster code base, see [cppcheck.log|https://ci.modcluster.io/job/mod_proxy_cluster-2.x-windows/DISTRO=apache-lounge,label=w2k12r2/93/artifact/cppcheck.log/*view*/], and among *many* warnings and style check failures, there was a one outstanding error reported, which set me wondering. > The error occurs on two places and I'm scratching my head as to whether is is a false positive or not, WDYT? > * [native/mod_manager/domain.c:198|https://github.com/modcluster/mod_proxy_c...]: (error) Address of local auto-variable assigned to a function parameter. > * [native/mod_manager/node.c:227|https://github.com/modcluster/mod_proxy_clu...]: (error) Address of local auto-variable assigned to a function parameter. > Is it O.K. to handle local, function scope, automatically allocated variable this way? To use it's address later in ap_slotmem_do? Couldn't it trigger undefined behaviour and cause some of our rare, hard to reproduce crashes? > Feel free to pick up any other pertinent messages from the log. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-625) Automatically allocated function local variable address overwrires function parameter

by Michal Karm Babacek (JIRA)

Michal Karm Babacek created MODCLUSTER-625: ---------------------------------------------- Summary: Automatically allocated function local variable address overwrires function parameter Key: MODCLUSTER-625 URL: https://issues.jboss.org/browse/MODCLUSTER-625 Project: mod_cluster Issue Type: Bug Components: Native (httpd modules) Environment: C99 (apparently both GNU and MSVC) Reporter: Michal Karm Babacek Assignee: George Zaronikas Fix For: 2.0.0.Alpha1 I went through the cppcheck static analysis report on the current mod_proxy_cluster code base, see [cppcheck.log|https://ci.modcluster.io/job/mod_proxy_cluster-2.x-windows/DISTRO=apache-lounge,label=w2k12r2/93/artifact/cppcheck.log/*view*/], and among *many* warnings and style check failures, there was a one outstanding error reported, which set me wondering. The error occurs on two places and I'm scratching my head as to whether is is a false positive or not, WDYT? * [native/mod_manager/domain.c:198|https://github.com/modcluster/mod_proxy_c...]: (error) Address of local auto-variable assigned to a function parameter. * [native/mod_manager/node.c:227|https://github.com/modcluster/mod_proxy_clu...]: (error) Address of local auto-variable assigned to a function parameter. Is it O.K. to handle local, function scope, automatically allocated variable this way? To use it's address later in ap_slotmem_do? Couldn't it trigger undefined behaviour and cause some of our rare, hard to reproduce crashes? Feel free to pick up any other pertinent messages from the log. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-624) mod_proxy_cluster: Introduce basic static analysis to upstream CI

by Michal Karm Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-624?page=com.atlassian.jira.pl... ] Michal Karm Babacek updated MODCLUSTER-624: ------------------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Done, see for example: [cppcheck.log|https://ci.modcluster.io/job/mod_proxy_cluster-2.x-windows/DISTRO=apache-lounge,label=w2k12r2/93/artifact/cppcheck.log/*view*/] > mod_proxy_cluster: Introduce basic static analysis to upstream CI > ----------------------------------------------------------------- > > Key: MODCLUSTER-624 > URL: https://issues.jboss.org/browse/MODCLUSTER-624 > Project: mod_cluster > Issue Type: Bug > Components: CI & Packaging > Affects Versions: 2.0.0.Alpha1 > Environment: Windows > Reporter: Michal Karm Babacek > Assignee: Michal Karm Babacek > Priority: Critical > > cppcheck report is a must -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-624) mod_proxy_cluster: Introduce basic static analysis to upstream CI

by Michal Karm Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-624?page=com.atlassian.jira.pl... ] Michal Karm Babacek updated MODCLUSTER-624: ------------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/modcluster/ci.modcluster.io/pull/30, https://github.com/modcluster/ci.modcluster.io/pull/31 > mod_proxy_cluster: Introduce basic static analysis to upstream CI > ----------------------------------------------------------------- > > Key: MODCLUSTER-624 > URL: https://issues.jboss.org/browse/MODCLUSTER-624 > Project: mod_cluster > Issue Type: Bug > Components: CI & Packaging > Affects Versions: 2.0.0.Alpha1 > Environment: Windows > Reporter: Michal Karm Babacek > Assignee: Michal Karm Babacek > Priority: Critical > > cppcheck report is a must -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-623) Ditch 32bit mod_proxy_cluster builds

by Michal Karm Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-623?page=com.atlassian.jira.pl... ] Michal Karm Babacek updated MODCLUSTER-623: ------------------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Ditch 32bit mod_proxy_cluster builds > ------------------------------------ > > Key: MODCLUSTER-623 > URL: https://issues.jboss.org/browse/MODCLUSTER-623 > Project: mod_cluster > Issue Type: Bug > Components: CI & Packaging > Affects Versions: 2.0.0.Alpha1 > Environment: Windows > Reporter: Michal Karm Babacek > Assignee: Michal Karm Babacek > > Trimming down the build & test matrix. 32bit builds are being deprecated and removed from CI. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-623) Ditch 32bit mod_proxy_cluster builds

by Michal Karm Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-623?page=com.atlassian.jira.pl... ] Michal Karm Babacek updated MODCLUSTER-623: ------------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/modcluster/ci.modcluster.io/pull/29 > Ditch 32bit mod_proxy_cluster builds > ------------------------------------ > > Key: MODCLUSTER-623 > URL: https://issues.jboss.org/browse/MODCLUSTER-623 > Project: mod_cluster > Issue Type: Bug > Components: CI & Packaging > Affects Versions: 2.0.0.Alpha1 > Environment: Windows > Reporter: Michal Karm Babacek > Assignee: Michal Karm Babacek > > Trimming down the build & test matrix. 32bit builds are being deprecated and removed from CI. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues October 2017