[Bug linuxthreads/28795] New: Segmentation fault with gcc 4.8.5 during pthread_cleanup_push and pthread_mutex_unlock

[Bug linuxthreads/28795] New: Segmentation fault with gcc 4.8.5 during pthread_cleanup_push and pthread_mutex_unlock

[ourgour at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=28795

            Bug ID: 28795
           Summary: Segmentation fault with gcc 4.8.5 during
                    pthread_cleanup_push and pthread_mutex_unlock
           Product: glibc
           Version: 2.22
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: linuxthreads
          Assignee: unassigned at sourceware dot org
          Reporter: ourgour at gmail dot com
                CC: drow at false dot org
  Target Milestone: ---

Created attachment 13917
  --> https://sourceware.org/bugzilla/attachment.cgi?id=13917&action=edit
C File to reproduce described issue

Hi,

I'm working on SUSE Linux 12.4 platform with gcc 4.8.5 and glibc 2.22.

I have threading application which fails during pthread_mutex_unlock (which is
pushed via pthread_cleanup_push)

I've attached source file.

Failure can be reproduced when compiled like :

gcc -m32 -pthread sapl.c -o sapl.o


If it's compiled without -m32 option, it works fine.


Also, issue is reproducing for a single thread too.


Please help out.

Thanks,
Digvijay

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug nptl/28795] Segmentation fault with gcc 4.8.5 during pthread_cleanup_push and pthread_mutex_unlock

[fweimer at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=28795

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2022-01-20
             Status|UNCONFIRMED                 |WAITING
              Flags|                            |security-
                 CC|                            |drepper.fsp at gmail dot com,
                   |                            |fweimer at redhat dot com
     Ever confirmed|0                           |1
          Component|linuxthreads                |nptl

--- Comment #1 from Florian Weimer <fweimer at redhat dot com> ---
I can't reproduce this with more recent distribution builds.

There were some issues with the old x86 assembler implementations of locking
primitives, and we have since removed them.

I suggest to reach out to SUSE to see if they can apply relevant fixes to their
distribution. Thanks.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug nptl/28795] Segmentation fault with gcc 4.8.5 during pthread_cleanup_push and pthread_mutex_unlock

[ourgour at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=28795

--- Comment #2 from Digvijay Gour <ourgour at gmail dot com> ---
Hi,

Thanks for reply. I'll get in touch with SUSE then. Apart from that, is there
anyway to resolve this by upgrading glibc version or gcc version to get rid of
assembler issues you mentioned earlier?


Thanks.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug nptl/28795] Segmentation fault with gcc 4.8.5 during pthread_cleanup_push and pthread_mutex_unlock

[fweimer at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=28795

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |RESOLVED
         Resolution|---                         |MOVED

--- Comment #3 from Florian Weimer <fweimer at redhat dot com> ---
(In reply to Digvijay Gour from comment #2)
> Thanks for reply. I'll get in touch with SUSE then. Apart from that, is
> there anyway to resolve this by upgrading glibc version or gcc version to
> get rid of assembler issues you mentioned earlier?

That depends on the nature of the bug. Without knowing the actual cause, I
don't think it makes sense to speculate about (reliable) workarounds, sorry.

-- 
You are receiving this mail because:
You are on the CC list for the bug.