A test program of mine loads a shared library (.so file). A function call in the shared library throws an exception that I am trying to catch in the main function of my test program. (I know that exception is being thrown for sure, I wrote the library to do that.)
However in the main program, the exception is not being caught. The flow of program goes past the catch block like no error has occurred. I am using g++ and I load the shared file using -l option. Only trying to load the program statically I got the following error:
/usr/bin/ld: cannot find -lmy-shared-library collect2: ld returned 1 exit status
Writing a smart array class for my C++ class. I'm running into a problem where the constructor apparently throws the wrong exception. Compiled on G++ with C++11 extensions enabled.
Code: // headers #include <iostream> #include <utility> #include <cctype> // stuff we need from namespace std using std::cout; using std::cin;
[Code] .....
When I try to check the error-handling code, when I enter a size less then two, Array's ctor throws InvalidSize, and gets caught, all good. But when I enter a letter, the ctor also seems to throw InvalidSize!
I attempted to create a dynamic array class for use in my engine (due to problems regarding a dll-interface with the standard library), so I tried at making a standard-compatible allocator template class first. After I "finished" that, I went on to work on the dynamic array class itself.So I finish the dynamic array class, and test it with the standard allocator. It works perfectly, but when I test it with my custom allocator class, it fails terribly.
To make sure it wasn't my DynamicArray class that was causing issues, I tried using the custom allocator on the std::vector class template, and it didn't work either. IMy DynamicArray class code:
// Represents a dynamic array, similar to the standard library's "vector" class. template<typename T, typename A> class DynamicArray { public: DynamicArray() : data(nullptr), elements(0), capacity(0)
[code].....
The "Request" and "Free" functions are my engine's equivalent of malloc and free (or new and delete). I allocate a large buffer (16 mb), and through those functions I distribute the memory to where it's needed.
writing a program that requires exception handling. if an error occurs, i what the program to go back to the begging of the loop. i tried using break but that just makes the program crash when it receives a bad input. how do i do this? this is what i have so far (this part of the program any ways)
while (! quit) { // Output phone book menu cout << endl
I've always wanted to know how to write my own system for the learning experience. I've worked on simple ones that read from a flatfile of a defined size, but never one that was on a fully formatted drive.
Where do I start? Are there any examples/tutorials?
I have a matrix class who use the stl vector to manage its
memory(UInt is typedef of size_t): class Mtrx { protected:
[Code]....
However, the two different classes are only different with each other on the allocator. I am thinking, that a elegant way should be merging them together.
I am coding a singly-linked list container. Of course, internally it uses Node<T>.
Question: what is the correct way to use the allocator given by the user? I ask, because I've read this on the rival C++ Reference:
std::list<T, A> allocates nodes of some internal type Node<T>, using the allocator std::allocator_traits<A>::rebind_alloc<Node<T>>, which is implemented in terms of A::rebind<Node<T>>::other if A is an std::allocator
[URL]...
The above doesn't seem right to do, because then what should pointer and const_pointer be?
using pointer = std::allocator_traits<Alloc>::pointer; using const_pointer = std::allocator_traits<Alloc>::const_pointer; // but we're using Alloc<Node<T>> not Alloc<T> // so maybe do this? using pointer = value_type *; using const_pointer = const value_type *;
I catch an exception and want to log it on the console. This works as exepcted, but Valgrind shows me a set of invalid reads.
Here the code of the catch-block:
} catch(HGL::IOException &e) { logError(e); }
The signature of the logDebug is: BasicLogger &operator<<(const std::exception &e);
Now valgrind shows me 4 errors like that:
==20943== Invalid read of size 1 ==20943== at 0x402C658: strlen (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so) ==20943== by 0x41554DD: std::basic_ostream<wchar_t, std::char_traits<wchar_t> >& std::operator<< <wchar_t, std::char_traits<wchar_t> >(std::basic_ostream<wchar_t, std::char_traits<wchar_t> >&, char const*) (in /usr/lib/i386-linux-gnu/libstdc++.so.6.0.16)
[Code] .....
Generally I dislike invalid read in my code, even if they are harmless like in that case.
If I don't pass a reference, but a copy of the exception, I don't get this invalid reads, but also loose all information, because of the implicit upcasting.
Why I get the illegal read, resp. why std::wstring is deleting it on the way to the <<-operator?
I'm trying to do some operator overloading, the function is supposed to add the values at index [i] of two vectors and place the result in the returning vector. The problem is I keep getting a vector out of range. This is the overloaded operator I'm working with (relatively new to these):
vector<float> operator+(const vector<float>& a, const vector<float>& b){ unsigned long size; vector<float> temp; if(a.size() >= b.size()) size = a.size();
[Code] .....
and then I would do something like this in the main:
vector<float> v, v1, v2;
v1.push_back(9.1); ... v2.push_back(8); ... v = v1 + v2;
but when I try to output the vector v I just get a vector out of range exception.
I'm making an "improved" array for my programing class. It's currently unfinished, so you might see some commented out code. I'm trying to debug what I have.
I keep getting these errors when I try to complile my main.cpp:
In file included from main.cpp:3:0:
array.h:107:43: error: expected type-specifier before ‘out_of_range’ array.h:107:43: error: expected ‘)’ before ‘out_of_range’ array.h:107:43: error: expected initializer before ‘out_of_range’ array.h:121:55: error: expected type-specifier before ‘out_of_range’ array.h:121:55: error: expected ‘)’ before ‘out_of_range’ array.h:121:55: error: expected initializer before ‘out_of_range’
My main file:
#include <iostream> #include <stdexcept> #include "array.h" using namespace std; using namespace ArrayNameSpace; int main() { Array<int> testSubject(5); return 0; }//End main
aannnd my Array.h file:
//ADD CONSTS TO METHODS //CURRENTLY WORKING ON EXCEPTIONS AND BRACKET[] OVERLOADS. I HAVE TO FIGURE OUT SOLUTIONS FOR REACHING //INDEXES FOR CHARS AND ENUMS #ifndef __array_H__ #define __array_H__ #include <stdexcept> namespace ArrayNameSpace {
I have been assigned to create a search function in text file, but I received this error when I run the program and try to search: Error message: Unhandled exception at 0x0f85d442 (msvcr100d.dll) in Ticket.exe: 0xC0000005: Access violation reading location 0xcccccd08.
I don't know what is the exactly problem. So I just copy everything and paste here. Please don't fear of these codes, I have 2 files only, but I will paste 3 files here, the one is prototypes.h, then the main.cpp, the last one is part of my function that can working well alone, but when I put them into main.cpp I will get the error message like I mentioned before.
write a program as described below: program that reads in two integers (age, social security number). You should write functions that throw an out-of-range exception forage (no negative numbers)SSN (must be a 9-digit integer) My code is written below:
#include "std_lib_facilities_4.h" int main(){ int age = 0; int ssn = 0;
If a class A contains an array of objects of another class B.. And in the constructor of A, while constructing objects of B, any one object throws an exception, then how can we guarantee to release all the memory acquired.. so that there is no memory leak..
class B{}; class A{ public: B Array[100]; ... };
In the above code, if in constructor of A, suppose 99 objects of B are constructed successfully, but 100th object throws exception, then how can we guarantee to release all the memory acquired by the other 99 objects?
I have one problem deleting a file with boost. The file is opened in another application and cannot be deleted. I am supposed to received an exception error but I don't get it.
I have put a breakpoint inside the catch part but it does not come to this point. Instead, the the output window of visual studio, I got these lines:
First-chance exception at 0x00007FFD2E575A88 in site_server.exe: Microsoft C++ exception: boost::filesystem::filesystem_error at memory location 0x00000070F8E3E920. Unhandled exception at at 0x00007FFD2E575A88 in site_server.exe: Microsoft C++ exception: boost::filesystem::filesystem_error at memory location 0x00000070F8E3E920.
It is advisable not to throw the exception from destructor. Because if exception happens stack unwinding happens. suppose the destructor again throws the exception then on part of first exception again one exception is thrown and exceptions can not be handled at same time. This is what i read from stack over flow.
I have a date class and i overloaded operator >> to accept input in dd/mm/yyyy format. if i enter the wrong date format my program will crash. How do i do exception handling for this? How should i do the try part? and for catch, I'll just catch a date class variable?
Code: void operator >> (istream &is, clsDate &date) { string inputDate; is >> inputDate; int mm = stringToNumber(inputDate.substr(3,2)); // read 2 characters from character number 3 start int dd = stringToNumber(inputDate.substr(0,2)); // read 2 characters from character number 0 start int yy = stringToNumber(inputDate.substr(6,4)); // read 4 characters from character number 6 start
When creating an exception mask for a file, should an exception throw during a file operation, I can reset the state bits of the actual file using ios::clear().
Though after doing so, will the exception mask still throw an exception, thinking that the specified error state flags are still set to true? If so, how can I reset the exception mask so that it is ready to throw more exceptions should the appropriate situations arise in the future?