'memory corruption' error when using Awk Post: 302332532

Sponsored Content

Top Forums UNIX for Dummies Questions & Answers 'memory corruption' error when using Awk Post 302332532 by vgersh99 on Thursday 9th of July 2009 11:04:31 AM

07-09-2009

Moderator

To keep the forums high quality for all users, please take the time to format your posts correctly.

First of all, use Code Tags when you post any code or data samples so others can easily read your code. You can easily do this by highlighting your code and then clicking on the # in the editing menu. (You can also type code tags [code] and [/code] by hand.)

Second, avoid adding color or different fonts and font size to your posts. Selective use of color to highlight a single word or phrase can be useful at times, but using color, in general, makes the forums harder to read, especially bright colors like red.

Third, be careful when you cut-and-paste, edit any odd characters and make sure all links are working property.

Thank You.

The UNIX and Linux Forums

---------- Post updated at 11:04 AM ---------- Previous update was at 10:49 AM ----------

First of all, you're missing a '}' in the END block.
Secondly, in the END block you have a loop counting from 0 going through ALL the numbers to the highest REGARDLESS whether an ID was found or not. If the number/id has not been found, you still try to access the array indexed by this 'id'. My 'awk/nawk' on Solaris didn't complain - maybe your 'mawk' on whatever OS you're on is less 'forgiving'.
As an alternative try that:

Code:

END {
      #for  ( num = 0; num <= highest_packet_id; num++ ) {
      for  ( num in start_time) {
                start = start_time[num];
                end = end_time[num];
                 if ( start < end )
                        delay = end - start;
      }
}

OR (if you want to process the IDs in ascending order:

Code:

END {
      for  ( num = 0; num <= highest_packet_id; num++ ) {
                if (!(num in start_time)) continue
                start = start_time[num];
                end = end_time[num];
                 if ( start < end )
                        delay = end - start;
      }
}

You're not outputting anything in the END block, so it's hard to judge.

Last edited by vgersh99; 07-09-2009 at 12:17 PM..

vgersh99

View Public Profile for vgersh99

Find all posts by vgersh99

10 More Discussions You Might Find Interesting

1. Programming

Why does this occur? * glibc detected * malloc(): memory corruption: 0x10013ff8 ***

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 ...

2. UNIX for Advanced & Expert Users

Out of Memory error when free memory size is large

I was running a program and it stopped and showed "Out of Memory!". at that time, the RAM used by this process is around 4G and the free memory size of the machine is around 30G. Does anybody know what maybe the reason? this program is written with Perl. the OS of the machine is Solaris U8. And I...

3. Programming

readdir and dynamic array memory corruption

Hi everyone I am developing an utility. At some part of it I read directory entries to a dynamic array: struct list It stores pointers to items: list.entries, which are structures: struct entry If a number of files in a directory is greater then number of elements an array was initially...

4. Programming

./match_pattern.out: malloc(): memory corruption: 0x0000000013a11600 ***

Hi All, I have a simple code which does some computation by matching string patterns. In brief: 1. The code reads .dat and .txt files. 2. .dat files are huge text files and .txt files contain some important words. 3. I am just doing strstr to find the patterns. 4. The function returns the...

5. Programming

* glibc detected * ./a.out: malloc(): memory corruption (fast):

*** 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...

6. Programming

* glibc detected * : malloc(): memory corruption (fast)

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...

7. Programming

* glibc detected * ./a.out malloc() memory corruption

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); ...

8. Solaris

Solaris 10 Shared Memory Corruption with X11

I am having a problem with shared memory corruption. I have two 86 servers running Solaris 10 (150400-06). One of the servers is accessed by a Sun Ray thin client Version 11.1.3.0.2.6. I login into server one from the thin client. I then ssh -X to server two. When a process that contains a...

9. Programming

Memory corruption in dynamic array of strings

I put together a C function to add strings to a dynamic array of strings (mostly for educational purpose to explain pointers to my kid). It works, but sometimes one or two strings in the array becomes corrupted. Running example on 64 bit Ubuntu, gcc ver. 4.8.4 Hope my code is self-explanatory: ...

10. Solaris

Solaris 11.2 x86 Local Zones for Oracle RAC database, intermittent Memory corruption of db

Hi, I was wondering if any Solaris fellow out there has dealt with running Solaris 11 x86 on Local Zones for Oracle RAC (which may or may not be relevant to issue), running on HP gen h/w. Every so often could be weeks between issues or some times days, there will be a memory corruption and db...

LEARN ABOUT MOJAVE

set_color

set_color(1)							       fish							      set_color(1)

NAME

       set_color - set_color - set the terminal color

set_color - set the terminal color
   Synopsis
       set_color [-v --version] [-h --help] [-b --background COLOR] [COLOR]

   Description
       Change the foreground and/or background color of the terminal. COLOR is one of black, red, green, brown, yellow, blue, magenta, purple,
       cyan, white and normal.

       o -b, --background Set the background color

       o -c, --print-colors Prints a list of all valid color names

       o -h, --help Display help message and exit

       o -o, --bold Set bold or extra bright mode

       o -u, --underline Set underlined mode

       o -v, --version Display version and exit

       Calling set_color normal will set the terminal color to whatever is the default color of the terminal.

       Some terminals use the --bold escape sequence to switch to a brighter color set. On such terminals, set_color white will result in a grey
       font color, while set_color --bold white will result in a white font color.

       Not all terminal emulators support all these features. This is not a bug in set_color but a missing feature in the terminal emulator.

       set_color uses the terminfo database to look up how to change terminal colors on whatever terminal is in use. Some systems have old and
       incomplete terminfo databases, and may lack color information for terminals that support it. Download and install the latest version of
       ncurses and recompile fish against it in order to fix this issue.

Version 1.23.1							  Sun Jan 8 2012						      set_color(1)

10 More Discussions You Might Find Interesting

1. Programming

Why does this occur? * glibc detected * malloc(): memory corruption: 0x10013ff8 ***

Discussion started by: cdbug

2. UNIX for Advanced & Expert Users

Out of Memory error when free memory size is large

Discussion started by: lilili07

3. Programming

readdir and dynamic array memory corruption

Discussion started by: torbium

4. Programming

./match_pattern.out: malloc(): memory corruption: 0x0000000013a11600 ***

Discussion started by: shoaibjameel123