Home/ Questions/Q 165325
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T11:54:04+00:00

I have a program which is like this list<int>:: iterator n = alist.begin(); while(n!=

  • 0

I have a program which is like this

list<int>:: iterator n = alist.begin(); while(n!= (list<int>::iterator)0) {     printf('Element is %d\n',*n);     n = alist.erase(n); }

So here i am comparing iterator with zero. but after deleting the last element the compiler is showing this error.

 *** glibc detected *** ./new: free(): invalid pointer: 0xbf99cb10 *** ======= Backtrace: ========= /lib/libc.so.6[0xb7d956e1] /lib/libc.so.6(cfree+0x89)[0xb7d96d79] /usr/lib/libstdc++.so.6(_ZdlPv+0x21)[0xb7f3ff81] ./new[0x8048c81] ./new[0x8048ca6] ./new[0x8048d07] ./new[0x8048d39] ./new(__gxx_personality_v0+0x216)[0x804888e] /lib/libc.so.6(__libc_start_main+0xdc)[0xb7d46f9c] ./new(__gxx_personality_v0+0x49)[0x80486c1] ======= Memory map: ======== 08048000-0804a000 r-xp 00000000 08:09 3704751    /home/sathya/chaithra/archivesthrash/new

If I want the iterator to be zero if the queue/list is empty.. what i should do? Because in my project I need to compare this iterator with zero only and not with alist.end().. What may be the probable solution to this…?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Why do you think the iterator will ever ‘be zero’? Iterators are not pointers or indexes. If you need to check if a container is empty, use the empty() member function.

    • 0