11-26-2014
From the fact that the error happens after the test program emits "hello world", I'm more suspicious of the problem being a static destructor called when the process exits.
Replace the call to the "pmap" utility with a call to "pstack" and the call stack when the error is detected will be shown.
This User Gave Thanks to achenle For This Post:
10 More Discussions You Might Find Interesting
1. Programming
hi,
I have made a small C program that make use of malloc and free for processing bitmap images. when i try to run the program, I am getting a error something like
*** glibc detected *** free(): invalid next size (normal): 0x0000000000503e70 ***
I am not sure of which free() is causing this... (1 Reply)
Discussion started by: vbreddy
1 Replies
2. Programming
when i try to use the class i wrote, i either get this:
*** glibc detected *** double free or corruption: 0x40236ff4 ***
and the proccess exits with an error code of 0;
or it segfaults. could someone look at my header file (with imp.) to give me some insight as to why its not working?
... (19 Replies)
Discussion started by: norsk hedensk
19 Replies
3. Programming
I am using a structure defined as follows
struct gene_square
{
double *x;
double *y;
};I have class, with a member function which is a pointer of this type:
gene_square* m_Genes;I am allocating memory in the constructors like this:
m_Genes = new gene_square;
for (ii=0;... (1 Reply)
Discussion started by: jatoo
1 Replies
4. Programming
there seems not to be error in this segment. In some computers, it can work well. But in others, it will give a failure.
why it ocurrs and how to deal with it?
in a function:
if( *ver == NULL ) {
*ver = (vertex *) malloc(sizeof(vertex)); //this line
... (17 Replies)
Discussion started by: cdbug
17 Replies
5. Programming
Hi,
I am having a hell of a time getting this to work. So basically, I have opened a popen to run a program that is going to prompt an action to occur half way through, when it gets to this I need to create a separate process and do some stuff, then return to the original process. This works... (0 Replies)
Discussion started by: imrank27
0 Replies
6. Programming
*** glibc detected *** ./a.out: malloc(): memory corruption (fast):
Posted A minute ago
M trying to make multiway tree and dont know what happend when this part of code get executed:
01void ins(NODE *ptr)
02{
03 //working
04 if(ptr!=NULL)
05 {
06 SNODE *var=NULL;
07 var=(SNODE... (3 Replies)
Discussion started by: exgenome
3 Replies
7. Programming
Hi Friends,
while executing the below code, am getting *** glibc detected *** ./ok: malloc(): memory corruption (fast) error, please suggest how to solve this issue.
#include <stdio.h>
#include <string.h>
#include <sqlca.h>
#include <alloca.h>
/* Define constants for VARCHAR... (2 Replies)
Discussion started by: mpjobsrch
2 Replies
8. Programming
Hello.
I'm looking for a quite "interesting" bug I'm using fortran 90, compiler gfortran and the main idea is for every time step I build a bin structure for search contact between particles, for this at the begining
TYPE :: circle_index
INTEGER(kind = 4) :: ind_p
TYPE(circle_index),... (1 Reply)
Discussion started by: Marce
1 Replies
9. Programming
I am facing a problem of memory corruption. The loop runs for the first time but does not go through the second time. What could be the problem?
for(int z=0;z<2;z++)
{
fp=fopen("poly.dat","r");
/*do something which reads this file into a 2D array*/
fclose(fp);
... (10 Replies)
Discussion started by: dare
10 Replies
10. Homework & Coursework Questions
Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted!
1. The problem statement, all variables and given/known data:
I'm doing aproximation of derivative called five-point stencil. For every value of x, in interval , in step... (0 Replies)
Discussion started by: antonija
0 Replies
pstack(1) General Commands Manual pstack(1)
NAME
pstack - print a stack trace for each LWP in each process and core file
SYNOPSIS
DESCRIPTION
prints a stack trace (hex+symbolic) for each LWP (Lightweight Process) in each process and core file.
Given the pid of a running process or the full path of a core file, prints the stack trace for each LWP thread in the process. To obtain
symbol information, searches load modules (executable and shared libraries) in the current directory, and You can specify the executable
path with the pid/corepath, separated by a colon character. If cannot find a load module, symbol information for frames in that module is
not displayed.
works by attaching to the running process and reading its registers, memory, and stack. Mismatch between executable and corefile may
result in unpredictable behavior.
Options
supports the following option:
Prints the usage menu.
Operand
supports the following operand:
pid identifies a running process, with an optional execpath, the full executable path.
corepath is the full path name of the specified executable.
RETURN VALUES
returns the following values:
Successful completion.
Failure.
An error has occurred.
SEE ALSO
ldd(1), pldd(1).
Itanium(R)-based Systems Only pstack(1)