08-10-2005
Memory problems are always a bugger to find, usually because the point of failure is not the fault, the fault lies elsewhere in your code.
One thing you can try - which is rather crude - is to comment out lines of code, recompile and run. If you continue to comment out lines of code sooner or later you will comment out the faultly line of code and the problem goes away.
In my own experience once you have identified the line of code causing your problem, a fix is not far behind.
This method has its limitations, of course, but it may help.
MBB
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I'm a complete beginner at all this business so any help is appreciated.
I have a script (not written by me) which I need to modify. My problems is....
tail -1c $file
.... I understand this will return the final character of the $file variable. I need to make it return the first... (4 Replies)
Discussion started by: mastaCow
4 Replies
2. Programming
Hi, I try to marshal a unsigned int and a char * into a buffer, and then unmarshal them later to get them out. I need to put the char * in the front and unsigned int at the end of the buffer. However, my system always give me "BUS ERROR". I am using Sun Sparcs Sloris 2.10.
My code to marshal... (6 Replies)
Discussion started by: nj302
6 Replies
3. UNIX for Dummies Questions & Answers
Hello everbody:
when issuing the ulimit -a, on my tru64 machone, I get the following:
root@billing4# ulimit -a
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) 10485760
stack(kbytes) 32768
memory(kbytes) 10190528
coredump(blocks) 0... (1 Reply)
Discussion started by: aladdin
1 Replies
4. Programming
helo can u tell me what do you mean by stack winding and stack unwinding
Regards,
Amit (2 Replies)
Discussion started by: amitpansuria
2 Replies
5. HP-UX
Hi,
I get a problem with stack overflow on HP-UX, when running a C program.
Pid 28737 received a SIGSEGV for stack growth failure.
Possible causes: insufficient memory or swap space,
or stack size exceeded maxssiz.
The possible cause i found, was that the definition of a structure had... (0 Replies)
Discussion started by: karthikb23
0 Replies
6. UNIX for Dummies Questions & Answers
I have a java process that piles up the stack memory.
ulimit -a
core file size (blocks, -c) unlimited
data seg size (kbytes, -d) unlimited
file size (blocks, -f) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 10
stack size ... (9 Replies)
Discussion started by: mohtashims
9 Replies
7. UNIX for Dummies Questions & Answers
Hi,
I am new to the linux kernel development area. I want to know what is the difference between kernel mode stack and user mode stack? Does each process has a user mode stack and a kernel mode stack?? Or Each process has a user mode stack and there is only one kernel mode stack that is shared by... (4 Replies)
Discussion started by: saurabhkoar
4 Replies
8. Android
Running latest Android for Galaxy Tab 8.9 and bought a 32GB USB flash memory stick for file transfers, etc. Would not work. Searched the net for clues and could not find any. Then, back at the IT store, found out that Galaxy Tab currently only supports up to 16GB for the USD flash memory stick.... (0 Replies)
Discussion started by: Neo
0 Replies
LEARN ABOUT DEBIAN
vtprintcap
VTPRINTCAP(5) File Formats Manual VTPRINTCAP(5)
NAME
vtprintcap - database of terminal printer control codes
SYNOPSIS
/etc/vtprintcap
DESCRIPTION
vtprintcap is a simple flat file database containing a list of the names of various terminals and the codes those terminals use to start
and stop an attached printer (media hard copy). This database is used by vtprint(1) and related programs.
Each entry is composed of three lines. The first line is a comma-delimited list of names which may be used to reference this entry. The
second line the sequence of characters used by the terminal to turn on an attached hard copy device and redirect output to that device.
The third line contains the sequence of characters used to turn the device off and restore normal output to the screen.
An entry must have all three lines to be considered valid. Currently no comment lines are permitted to exist between these lines: such
lines would be interpreted as the printer control codes themselves!
The rules for selecting a terminal name are simple: you must follow the same rules as for /etc/termcap(5) names. Terminal names should be
entered in /etc/vtprintcap with exactly the same names as are in /etc/termcap.
The control code strings in the second and third lines of an entry are governed as follows: ANSI C style escapes for character constants
(e.g.
for newline) are permitted, constant strings are permitted, and quotes may be used to as delimiters in the string. (This is use-
ful if you wish you use a digit immediately following a numeric escape. For example, ESC-5 should be represented as 33"5" to avoid confu-
sion in with 335. In general, the rules outlined for ANSI constant escaping are enforced.
Additionally, /etc/vtprintcap may contain comment lines, which are indicated by placing a hash mark (#) in the first column of the line.
Remember however that entries must not be broken up by comment lines!
EXAMPLE
Here is a sample entry common to DEC vt100 and vt102 terminals:
# Sample vtprintcap entry for vt100 & vt102 terminals
vt100, vt102
33[5i
33[4i
This entry would be used whenever the user's TERM environment variable was set to "vt102" or "vt100", using ESC [5i and ESC [4i as the
printer control codes to turn a printer on and off, respectively.
DISTRIBUTION
vtprintcap is part of the vtprint package, which can be obtained by anonymous ftp at ftp.sdsu.edu in the /pub/vtprint directory. Please
read the INDEX and README files before downloading.
If you do not have ftp availability, then you can request a uuencoded copy of vtprint be sent to you via e-mail from the author. The
author is also willing to make other arrangements as needed, within certain limitations.
FILES
/etc/termcap
/etc/vtprintcap
BUGS
vtprintcap handling code currently could get confused if a printer control code is exactly the same as the name of a terminal, or contained
the name of a terminal delimited by commas. As this is very unlikely to every occur, it shouldn't be a problem.
SEE ALSO
termcap(5) vtprint(1)
vtprint v2.0.2 25 October 1994 VTPRINTCAP(5)