public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libstdc++/63617] New: Crash in libstdc++ on AIX.
@ 2014-10-22 13:24 adivilceanu at yahoo dot com
  2014-10-22 14:15 ` [Bug libstdc++/63617] " redi at gcc dot gnu.org
  2014-11-07 14:54 ` adivilceanu at yahoo dot com
  0 siblings, 2 replies; 3+ messages in thread
From: adivilceanu at yahoo dot com @ 2014-10-22 13:24 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63617

            Bug ID: 63617
           Summary: Crash in libstdc++ on AIX.
           Product: gcc
           Version: 4.6.3
            Status: UNCONFIRMED
          Severity: major
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: adivilceanu at yahoo dot com

Hello,

We have a program "myapp" build with gcc 4.6.3 on AIX 6.1 Tl05.

At runtime the program crashed once very weird with the following stack:

pth_signal.pthread_kill(??, ??) at 0xd053c8d4
pth_signal._p_raise(??) at 0xd053bd64
raise.raise(??) at 0xd01209a0
abort.abort() at 0xd017c164
unnamed block in vterminate._ZN9__gnu_cxx27__verbose_terminate_handlerEv(),
line 95 in "vterminate.cc"
vterminate._ZN9__gnu_cxx27__verbose_terminate_handlerEv(), line 95 in
"vterminate.cc"
eh_terminate._ZN10__cxxabiv111__terminateEPFvvE(handler = ??), line 40 in
"eh_terminate.cc"
eh_terminate._ZSt9terminatev(), line 50 in "eh_terminate.cc"
unnamed block in
bitmap_allocator._ZN9__gnu_cxx8__detail13__mini_vectorISt4pairIPNS_16bitmap_allocatorIwE12_Alloc_blockES6_EE6insertEPS7_RKS7_(this
= @0x32d17f78, __pos = ??, __x = ??), line 116 in "bitmap_allocator.cc"
bitmap_allocator._ZN9__gnu_cxx8__detail13__mini_vectorISt4pairIPNS_16bitmap_allocatorIwE12_Alloc_blockES6_EE6insertEPS7_RKS7_(this
= @0x32d17f78, __pos = ??, __x = ??), line 116 in "bitmap_allocator.cc"
thread._ZN6Thread11mainFEPv(??) at 0xd114422c

The "Thread::mainF" is a thread routine that was passed to pthread_create.
We consider our code inside this method clean.

Please advise what kind of system call from our side could have generated this
stack. I mean we do not call directly any "bitmap_allocator".

Our program(myapp) has the following dependencies:
bash-4.2# ldd myapp
myapp needs:
         /usr/lib/threads/libc.a(shr.o)
         /usr/lib/libpthread.a(shr_xpg5.o)
         /usr/mypath/libstdc++.a(libstdc++.so.6)
         /usr/mypath/libgcc_s.a(shr.o)
         /usr/lib/libiconv.a(shr4.o)
         /usr/lib/libpthread.a(shr_comm.o)
         /usr/lib/libqb.a(shr.o)
         /unix
         /usr/lib/libcrypt.a(shr.o)
         /usr/lib/libpthreads.a(shr_comm.o)
         /usr/lib/libpthreads_compat.a(shr.o)
         /usr/lib/libz.a(libz.so.1)
         /usr/lib/libpthreads.a(shr.o)
The libstdc++.a and libgcc_s.a are taken from the gcc 4.6.3 compiler.

Thank you !


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

* [Bug libstdc++/63617] Crash in libstdc++ on AIX.
  2014-10-22 13:24 [Bug libstdc++/63617] New: Crash in libstdc++ on AIX adivilceanu at yahoo dot com
@ 2014-10-22 14:15 ` redi at gcc dot gnu.org
  2014-11-07 14:54 ` adivilceanu at yahoo dot com
  1 sibling, 0 replies; 3+ messages in thread
From: redi at gcc dot gnu.org @ 2014-10-22 14:15 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63617

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING
   Last reconfirmed|                            |2014-10-22
     Ever confirmed|0                           |1

--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
GCC 4.6 is no longer supported, so unless you can reproduce this with a current
release noone is going to investigate.

I'm assuming you've configured GCC to use the bitmap_allocator as the default
C++ allocator, so one likely cause is that an exception was thrown due to
failure to allocate memory.

In any case, please provide the information requested by
https://gcc.gnu.org/bugs/


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

* [Bug libstdc++/63617] Crash in libstdc++ on AIX.
  2014-10-22 13:24 [Bug libstdc++/63617] New: Crash in libstdc++ on AIX adivilceanu at yahoo dot com
  2014-10-22 14:15 ` [Bug libstdc++/63617] " redi at gcc dot gnu.org
@ 2014-11-07 14:54 ` adivilceanu at yahoo dot com
  1 sibling, 0 replies; 3+ messages in thread
From: adivilceanu at yahoo dot com @ 2014-11-07 14:54 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63617

--- Comment #2 from Adi <adivilceanu at yahoo dot com> ---
Can you tell me what are the "supported" version(s) now?

Also can you give me a kind of gcc supported version life cycle/chart/roadmap ?

Thank you,
Adi


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

end of thread, other threads:[~2014-11-07 14:54 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-10-22 13:24 [Bug libstdc++/63617] New: Crash in libstdc++ on AIX adivilceanu at yahoo dot com
2014-10-22 14:15 ` [Bug libstdc++/63617] " redi at gcc dot gnu.org
2014-11-07 14:54 ` adivilceanu at yahoo 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).