bus error, resize vector

[imutate]

I get a bus (or is it buss) error when I resize a vector

typedef std::vector<dou bledblvec;
n = 127;
dblvec rv;
rv.resize(n); // error happens here

Any clues ? I can post more info if required ?

[Thomas J. Gritzan]

im*****@hotmail .co.uk wrote:

>Now change all the op[] calls with at(). If you use all vectors, you can
do that with a global replace of '[' with "at(" and then globally
replace ']' with ")".

Do you mean change x[i] to x(i) or something else ?

He meant with:

std::vector<int vec;
int index = 42;

Change all occurences of
vec[index]
to
vec.at(index)

The at function does the same thing as operator[] but will throw an
exception when the index is out of bounds.

--
Thomas
http://www.netmeister.org/news/learn2quote.html

[imutate]

That will likely find your error real quick.

OK, yes it does not get far atall, I get an error (but no hint as to
what variable or part of the program)

terminate called after throwing an instance of std::out_of_ran ge
what(): vector::_M_rang e_check
Aborted

[Kai-Uwe Bux]

im*****@hotmail .co.uk wrote:

>That will likely find your error real quick.

OK, yes it does not get far atall, I get an error (but no hint as to
what variable or part of the program)

terminate called after throwing an instance of std::out_of_ran ge
what(): vector::_M_rang e_check
Aborted

Hint: run the program in a debugger. Then get a calltrace from the moment
when it aborts. This should tell you which function has the bug.
Best

Kai-Uwe Bux

[Daniel T.]

im*****@hotmail .co.uk wrote:

>That will likely find your error real quick.

OK, yes it does not get far atall, I get an error (but no hint as to
what variable or part of the program)

terminate called after throwing an instance of std::out_of_ran ge
what(): vector::_M_rang e_check Aborted

You are trying to access an array out of its bounds. Either use a
debugger and have it break on all exceptions, or go into the code at the
last place you know worked (based on how much output you got before it
crashed) and start looking at all the "at()" calls. The value passed
into one of them is too large.

--
There are two things that simply cannot be doubted, logic and perception.
Doubt those, and you no longer*have anyone to discuss your doubts with,
nor any ability to discuss them.

[imutate]

Daniel T. wrote:

You are trying to access an array out of its bounds. Either use a
debugger and have it break on all exceptions, or go into the code at the
last place you know worked (based on how much output you got before it
crashed) and start looking at all the "at()" calls. The value passed
into one of them is too large.

I put a std::cout and std::endl in the template ( [] function) and I
got a compiler message even though I included iostream. Why do I need
to change to at() calls if these are in the template ?

[Daniel T.]

In article <11************ **********@m73g 2000cwd.googleg roups.com>,
im*****@hotmail .co.uk wrote:

Daniel T. wrote:

You are trying to access an array out of its bounds. Either use a
debugger and have it break on all exceptions, or go into the code at the
last place you know worked (based on how much output you got before it
crashed) and start looking at all the "at()" calls. The value passed
into one of them is too large.

I put a std::cout and std::endl in the template ( [] function) and I
got a compiler message even though I included iostream. Why do I need
to change to at() calls if these are in the template ?

In your code you have something like:

myVec.at( i )

In the line before that, put:

assert( i < myVec.size() );

Do that everywhere you are using "at()".

When the code breaks, it will tell you what file and line number in that
file the problem is located at.

--
There are two things that simply cannot be doubted, logic and perception.
Doubt those, and you no longer*have anyone to discuss your doubts with,
nor any ability to discuss them.

[imutate]

OK, I got this debug template working. It would be nice to see the
variable name of the offending object.

[Howard]

<im*****@hotmai l.co.ukwrote in message
news:11******** **************@ e3g2000cwe.goog legroups.com...

OK, I got this debug template working. It would be nice to see the
variable name of the offending object.

Is this in response to something? What "debug template"? Do you have a
question?

Please provide some context in your responses, by quoting the relevant
portion(s) of what you're responding to. This isn't a chat room, and it's a
pain in the butt to try to go back and forth between messages to see where
the conversation has been going. Check out other posts here (such as this
one :-)) to see what I mean.

Thanks,
-Howard

[imutate]

Is this in response to something? What "debug template"? Do you have a

question?

Please provide some context in your responses, by quoting the relevant
portion(s) of what you're responding to. This isn't a chat room, and it's a
pain in the butt to try to go back and forth between messages to see where
the conversation has been going. Check out other posts here (such as this
one :-)) to see what I mean.

Thanks,
-Howard

It is one of these snazy gadgets (don't correct this code, as I pasted
from another message)
essentially..

#include <vector>

template < typename T >
class Vec : public std::vector< T {
public:
Vec() { }
Vec( int s ) : std::vector<T>( s) { }
T& operator[](int i) { return this -at(i); }
const T& operator[](int i ) const { return this -at(i); }
};

This was something I abandoned, but I got it working. So I based my
vectors on this now, for debugging.

typedef Vec<doublevecdb l;
typedef Vec<vecdblmatdb l;

[imutate]

Daniel T. wrote:

In your code you have something like:

myVec.at( i )

No because I got that template working, see my reply to Howard. (but
you know the one)

In the line before that, put:

assert( i < myVec.size() );

Do that everywhere you are using "at()".

When the code breaks, it will tell you what file and line number in that
file the problem is located at.

That won't do it, I already output at every place I write to these
vectors and there is no indication that I am assigning 3276..whatever
(actually 2^31 - 1 or such like).
Something else is corrupting this vector.