Maybe a problem with libgcc.a

2005-03-16 Thread BrownB
Hello, I've got this problem: I'm compiling CPP files and C files, with PRCTools, but whenever my application tries to use "new" it happens a Fatal Exception, because of a jump to a strange location (0x030006e50). Anyone has ideas? It's 5 days I'm blocked on this problem... Thank you for help,

Re: Maybe a problem with libgcc.a

2005-03-16 Thread Cory Pratt
I use "new" all the time. The only issue I've seen is that if you run out of memory, new still calls the constructor for the object. So, in all of my constructors I have: if (!this) return; BrownB wrote: > Hello, I've got this problem: I'm compiling CPP files and C files, with > PRCToo

Re: Maybe a problem with libgcc.a

2005-03-16 Thread BrownB
My problem isn't related to the memory usage, because if I use MemPtrNew() to allocate the object, I have no errors. In which segment do you place the contructor? Is this detail important? -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.co

Re: Maybe a problem with libgcc.a

2005-03-17 Thread Cory Pratt
MemPtrNew doesn't call the constructor. Perhaps there is a bug in your constructor. I put my constructors in the same segment as the other methods of the class but I don't think it matters. One problem I encountered with multiple segments was that I had a variable with the same name as a segment

Re: Maybe a problem with libgcc.a

2005-03-17 Thread BrownB
Thank you, but my contructor works well, the problem is not there. Debugging, I see that the problem is before calling the contructor: it seems to me it happen when the code uses the "new" operator defined in libgcc.a, making a jump to a strange location outside the program memory. I placed all