You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@stdcxx.apache.org by "Martin Sebor (JIRA)" <ji...@apache.org> on 2008/05/14 21:22:55 UTC

[jira] Closed: (STDCXX-180) [gcc 4.1/Solaris 9] SIGSEGV when SIGABRT expected

     [ https://issues.apache.org/jira/browse/STDCXX-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Sebor closed STDCXX-180.
-------------------------------

    Resolution: Cannot Reproduce

Works as expected with 4.2.x:
{noformat}
$ uname -srp && gcc -v && gmake t && ./t
SunOS 5.10 sparc
Using built-in specs.
Target: sparc-sun-solaris2.10
Configured with: ../src/gcc-4.1.1/configure --prefix=/nfs/packages/mdx/solaris/compilers/g++/4.1.1/ --enable-threads --enable-languages=c,c++
Thread model: posix
gcc version 4.1.1
gcc -c -I/amd/devco/sebor/stdcxx-4.2.x/include/ansi -D_RWSTDDEBUG   -pthreads -I/amd/devco/sebor/stdcxx-4.2.x/include -I/build/sebor/stdcxx-4.2.x-gcc-4.1.1-15s/include -I/amd/devco/sebor/stdcxx-4.2.x/examples/include  -pedantic -nostdinc++ -g   -W -Wall -Wcast-qual -Winline -Wshadow -Wwrite-strings -Wno-long-long   t.cpp
gcc t.o -o t -pthreads  -L/build/sebor/stdcxx-4.2.x-gcc-4.1.1-15s/lib  -lstd15s -lsupc++ -lm 
/amd/devco/sebor/stdcxx-4.2.x/include/vector:563: typename std::vector<_TypeT, _Allocator>::iterator std::vector<_TypeT, _Allocator>::erase(__rw::__rw_debug_iter<std::vector<_TypeT, _Allocator>, typename _Allocator::pointer, typename _Allocator::pointer>, __rw::__rw_debug_iter<std::vector<_TypeT, _Allocator>, typename _Allocator::pointer, typename _Allocator::pointer>) [with _TypeT = int, _Allocator = std::allocator<int>]: Assertion '_RW::__rw_valid_range (begin (), __first)' failed.
/build/sebor/stdcxx-4.2.x-gcc-4.1.1-15s/examples/t:_ZN4__rw16__rw_assert_failEPKcS1_iS1_+0x7c
/build/sebor/stdcxx-4.2.x-gcc-4.1.1-15s/examples/t:_ZNSt6vectorIiSaIiEE5eraseEN4__rw15__rw_debug_iterIS1_PiS4_EES5_+0xc4
/build/sebor/stdcxx-4.2.x-gcc-4.1.1-15s/examples/t:main+0xac
/build/sebor/stdcxx-4.2.x-gcc-4.1.1-15s/examples/t:_start+0x5c
Abort (core dumped)
{noformat}

> [gcc 4.1/Solaris 9] SIGSEGV when SIGABRT expected
> -------------------------------------------------
>
>                 Key: STDCXX-180
>                 URL: https://issues.apache.org/jira/browse/STDCXX-180
>             Project: C++ Standard Library
>          Issue Type: Bug
>          Components: Configuration
>    Affects Versions: 4.1.3
>         Environment: gcc 4.1/Solaris 9
>            Reporter: Martin Sebor
>            Assignee: Martin Sebor
>            Priority: Minor
>             Fix For: 4.2.2
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> The program below is expected to print the stack trace and exit with SIGABRT when compiled in debug mode. Instead it fails to print the stack trace and exits with SIGSEGV.
> $ cat v.cpp && nice make v && ./v
> #include <vector>
> int main ()
> {
>     std::vector<int> v1;
>     std::vector<int> v2;
>     v1.erase (v2.begin (), v2.end ());
> }
> gcc -c -I/build/sebor/dev/stdlib/include/ansi -D_RWSTDDEBUG   -pthreads -D_RWSTD_USE_CONFIG -I/build/sebor/gcc-4.1.0-15s/include -I/build/sebor/dev/stdlib/include -I/build/sebor/dev/stdlib/../rwtest -I/build/sebor/dev/stdlib/../rwtest/include -I/build/sebor/dev/stdlib/tests/include  -pedantic -nostdinc++ -g  -W -Wall -Wcast-qual -Winline -Wshadow -Wwrite-strings -Wno-long-long  v.cpp
> gcc v.o -o v -L/build/sebor/gcc-4.1.0-15s/rwtest -lrwtest15s -pthreads -L/build/sebor/gcc-4.1.0-15s/lib -lstd15s  -lsupc++ -lm
> /build/sebor/dev/stdlib/include/vector:618: typename std::vector<_TypeT, _Allocator>::iterator std::vector<_TypeT, _Allocator>::erase(__rw::__rw_debug_iter<std::vector<_TypeT, _Allocator>, typename _Allocator::pointer, typename _Allocator::pointer>, __rw::__rw_debug_iter<std::vector<_TypeT, _Allocator>, typename _Allocator::pointer, typename _Allocator::pointer>) [with _TypeT = int, _Allocator = std::allocator<int>]: Assertion '_RW::__rw_valid_range (begin (), __first)' failed.
> Segmentation Fault (core dumped)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.