public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libc/17327] New: __run_exit_handlers may miss new handlers
@ 2014-08-29  9:33 philip.pronin at gmail dot com
  2015-03-16 14:39 ` [Bug libc/17327] " sebastien.grivet at murex dot com
  2015-03-17  9:27 ` sebastien.grivet at murex dot com
  0 siblings, 2 replies; 3+ messages in thread
From: philip.pronin at gmail dot com @ 2014-08-29  9:33 UTC (permalink / raw)
  To: glibc-bugs

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

            Bug ID: 17327
           Summary: __run_exit_handlers may miss new handlers
           Product: glibc
           Version: 2.17
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
          Assignee: unassigned at sourceware dot org
          Reporter: philip.pronin at gmail dot com
                CC: drepper.fsp at gmail dot com

__run_exit_handlers keeps pointer to the list node it is traversing; some exit
handler may register new handlers, but these handlers may never be executed if
__new_exitfn had to calloc new list node.  __run_exit_handlers should start the
loop over (re-read head of the list) after the each processed handler.

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


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug libc/17327] __run_exit_handlers may miss new handlers
  2014-08-29  9:33 [Bug libc/17327] New: __run_exit_handlers may miss new handlers philip.pronin at gmail dot com
@ 2015-03-16 14:39 ` sebastien.grivet at murex dot com
  2015-03-17  9:27 ` sebastien.grivet at murex dot com
  1 sibling, 0 replies; 3+ messages in thread
From: sebastien.grivet at murex dot com @ 2015-03-16 14:39 UTC (permalink / raw)
  To: glibc-bugs

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

sebastien.grivet at murex dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |sebastien.grivet at murex dot com

--- Comment #1 from sebastien.grivet at murex dot com ---
Created attachment 8189
  --> https://sourceware.org/bugzilla/attachment.cgi?id=8189&action=edit
C++ testcase: several destructor miss

Hello,
I have encountered this bug by using log4cxx.
I wrote this test case to try to reproduce it.

This is a run:
A()
in ~A()
B(40)
... all constructors from 40 to 1
B(1)
out ~A()
~B(28)
... only destructors from 28 to 1
~B(1)


All destructors from 40 to 29 are missing.

Regards,
Sebastien.

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


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug libc/17327] __run_exit_handlers may miss new handlers
  2014-08-29  9:33 [Bug libc/17327] New: __run_exit_handlers may miss new handlers philip.pronin at gmail dot com
  2015-03-16 14:39 ` [Bug libc/17327] " sebastien.grivet at murex dot com
@ 2015-03-17  9:27 ` sebastien.grivet at murex dot com
  1 sibling, 0 replies; 3+ messages in thread
From: sebastien.grivet at murex dot com @ 2015-03-17  9:27 UTC (permalink / raw)
  To: glibc-bugs

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

--- Comment #2 from sebastien.grivet at murex dot com ---
Created attachment 8190
  --> https://sourceware.org/bugzilla/attachment.cgi?id=8190&action=edit
Proposed patch

This a proposed patch for stdlib/exit.c

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


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2015-03-17  9:27 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-08-29  9:33 [Bug libc/17327] New: __run_exit_handlers may miss new handlers philip.pronin at gmail dot com
2015-03-16 14:39 ` [Bug libc/17327] " sebastien.grivet at murex dot com
2015-03-17  9:27 ` sebastien.grivet at murex dot com

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).