bugCERTI - Bugs: bug #47597, Incorrect Setting of the...


bug #47597: Incorrect Setting of the Shm_Sem_Type in Main_SocketSHM.cc

Submitted by:  JbCh <jb_ch>
Submitted on:  Fri 01 Apr 2016 03:38:30 PM UTC  
Category:  None Severity:  3 - Normal
Item Group:  Software error Status:  Fixed
Privacy:  Public Assigned to:  JbCh <jb_ch>
Open/Closed:  Open Release:  GIT-master
Reproducibility:  Every Time Fixed Release:  GIT-master

Add a New Comment (Rich Markup)

You are not logged in

Please log in, so followups can be emailed to you.


Wed 03 Jan 2018 02:37:07 PM UTC, comment #1: 

Fixed on br_jbch_4.0.0 (commit #9827427) and tested under Fedora 23 64 bits (gcc  5.3.1).

Works fine.

JbCh <jb_ch>
Project AdministratorIn charge of this item.
Fri 01 Apr 2016 03:38:30 PM UTC, original submission:  

In current git trunk version (I don't know how to get git version number like for svn), there is an issue in the shm test processes implementation.

The Shm_Sem_Type is hardcoded to "Win32" in the main function (line 63)

When you run under Linux (I am using Fedora 23 64 bits but it doesn't matter) then the process stops when calling the RingBuffer Constructor because the semaphore type is incorrect.

It returns:

>> Shm_Sem_Type Must be Posix or SysV: No such file or directory

This should be fixed for a more generic approach.
I will take care of this.

JbCh <jb_ch>
Project AdministratorIn charge of this item.


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by jb_ch (Submitted the item)



    Follows 1 latest change.

    Date Changed by Updated Field Previous Value => Replaced by
    2018-01-03 jb_ch StatusNone => Fixed

    Back to the top

    Powered by Savane 3.6