free( ) : invalid size

[Ajith nandan]

Hi all,

I get an error called free( ) :  invalid size.

I have attached the image. 

Please, anyone, help me with this problem.

Thank you.

[Wolfgang Bangerth]

On 4/16/20 9:46 PM, Ajith nandan wrote:
> I get an error called free( ) :  invalid size.
> I have attached the image.
> Please, anyone, help me with this problem.

Ajith,
what have you already done? Have you run the program in a debugger to find out
where this happens and why? There clearly is a bug in your code, and you need
to find where and why. My best guess is that you are writing past the end of
an array and are overwriting other memory, but of course there is no way for
us to tell.

Best
W.

--
------------------------------------------------------------------------
Wolfgang Bangerth email: bang...@colostate.edu
www: http://www.math.colostate.edu/~bangerth/

[Ajith nandan]

Thanks, W for taking the time to look into it. I have attached the header file where I have to edit parts of the code in //Edit section.

Can you point out where I might have done an error?

Thank You.

--
The deal.II project is located at http://www.dealii.org/
For mailing list/forum options, see https://groups.google.com/d/forum/dealii?hl=en
---
You received this message because you are subscribed to the Google Groups "deal.II User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dealii+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dealii/a6a72b80-e3b3-7a68-4588-3edaa8fad975%40colostate.edu.

[Ajith nandan]

Hi

I forgot to add the support files.

Thank You

[Wolfgang Bangerth]

On 4/17/20 10:24 PM, Ajith nandan wrote:
> Thanks, W for taking the time to look into it. I have attached the header file
> where I have to edit parts of the code in //Edit section.
> Can you point out where I might have done an error?

Well, I hadn't actually offered to look into it, but I gave you a suggestion
in my previous email:

> what have you already done? Have you run the program in a debugger to find
> out
> where this happens and why? There clearly is a bug in your code, and you need
> to find where and why. My best guess is that you are writing past the end of
> an array and are overwriting other memory, but of course there is no way for
> us to tell.

Best

WB