Sponsored Content
Full Discussion: dbx fatal error
Operating Systems AIX dbx fatal error Post 302252675 by skfn1203 on Thursday 30th of October 2008 05:30:20 AM
Old 10-30-2008
dbx fatal error

Background
-------------
Os: IBM AIXL 5.1 (Unix)

Problem
-------------
I run the dbx in csh as follows

% dbx mainprog

-- The following is the systemm replay
Type 'help' for help.
reading symbolic information ...warning: stab entry unrecognized: name ,type 45, class a8, value 0'

dbx: fatal error: 1283-221 nesting depth underflow (0)


Questions
------------
How to solve it

Thak You
sam
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Fatal error in disk

I have a doubt with an error message, and i want to be sure if this is a normal situation or not. Situation: I was formating and installing a SCSI 36Gb HD with UNIX SCO 5.05, the problem happens when is making the division and filesystem on disk 1, and the message error is "Exit value 139... (1 Reply)
Discussion started by: jav_v
1 Replies

2. Programming

AIX DBX Error

I am trying to debug a program, which had generated a core dump. When I issue 'where' command, it list me filename along with line number, which in case is not at all there in the .c file. Example: (dbx) where func1(var1= (...), var2 = 86, var3 = 0,var4 = 0) , line 87 in "prog.f" main(),... (1 Reply)
Discussion started by: S.P.Prasad
1 Replies

3. Programming

ld: fatal error

dear all , iam trying to compile a progam using gcc compiler on a sun 280 R machine running solaris 9 . iam getting an error in the last step when the compiler tries to link the objects , although the compiler executes some applicarions that contains no objects smoothly, the error that... (1 Reply)
Discussion started by: ppass
1 Replies

4. UNIX for Advanced & Expert Users

Purify-SGI Fatal Error

Hi , attempting to purify code on the link line generates a fatal error like this #ERROR: (fatal) Cannot find libtest.so in the search path . command line: ------------- purify -show-directory=yes -always-use-cache-dir -cache-dir=/ppic/users/avadhani/sgi/pure /usr/bin/CC -n32 -mips3... (2 Replies)
Discussion started by: avadhani
2 Replies

5. Shell Programming and Scripting

Glance Fatal Error

Hi , I a stuck with this problem. I am trying to execute this script1 on SERVER 1 from SERVER 2 using script2 script1 on SERVER 1 #!/usr/bin/ksh /opt/perf/bin/glance -f -adviser_only -iterations 2 -maxpages 2 > /home/user/scripts/glance.op cpuval1=`grep ^CPU... (4 Replies)
Discussion started by: newbie07
4 Replies

6. Programming

Fatal Error

Hi, I just pulled out my code from source control, then I compiled, the compilation is successful at that time. Then I modified one of the source file, Then I compiled, I got the following error ld: fatal: Symbol referencing errors. No output written to ../../CM/bin/cato Before... (1 Reply)
Discussion started by: sarwan
1 Replies

7. Programming

ld: fatal error

i am trying to compile my program using a makefile and i keep getting this message: Undefined first referenced symbol in file main /usr/local/lib/gcc-lib/sparc-sun-solaris2.9/3.3/crt1.o ld: fatal: Symbol referencing errors. No output written to prog5 collect2: ld returned 1 exit status ***... (2 Replies)
Discussion started by: betterdayz
2 Replies

8. AIX

Error : fatal: record too large

while running a script to process a file , it ended in termination . I able to find from the logs that it ended due to the error : fatal: record too large 20480 . Then I tried lots to fix the issue and left in vain . Can any one help me in finding reason for it ? . If you provide me a solution , I... (1 Reply)
Discussion started by: sakthifire
1 Replies

9. UNIX for Dummies Questions & Answers

GCC compiler Ld fatal error

Hi all I'm trying to install sudo. When I first ran the sudo configure script it errored saying that I didn't have a C compiler. I have since installed the GCC 3.4.6 package for sol8 from sun freeware. Doing that resolved the no C complier found error. I was then getting an error saying... (1 Reply)
Discussion started by: Donkey25
1 Replies

10. What is on Your Mind?

PHP Fatal Errors During SSL Cert Management - PHP Fatal error: xc_fcntl_mutex failed

Today, I noticed some errors in our SSL cert renewal log files, mostly related to domains where the IP address had changed. Concerned about this, rebuilt out SSL cert, which normally goes well without a hiccup. However, for today, for some reason which I cannot explain, there was a PHP error... (0 Replies)
Discussion started by: Neo
0 Replies
STAB(5) 						      BSD File Formats Manual							   STAB(5)

NAME
stab -- symbol table types SYNOPSIS
#include <mach-o/stab.h> DESCRIPTION
The file <stab.h> defines some of the symbol table n_type field values for Mach-O a.out files. These are the types for permanent symbols (i.e. not local labels, etc.) used by the old debugger sdb and the Berkeley Pascal compiler pc(1). Symbol table entries can be produced by the .stabs assembler directive. This allows one to specify a double-quote delimited name, a symbol type, one char and one short of informa- tion about the symbol, and an unsigned long (usually an address). To avoid having to produce an explicit label for the address field, the .stabd directive can be used to implicitly address the current location. If no name is needed, symbol table entries can be generated using the .stabn directive. The loader promises to preserve the order of symbol table entries produced by .stab directives. As described in com- ments in <mach-o/nlist.h> an element of the symbol table consists of the following structure: /* * Format of a symbol table entry. */ struct nlist { union { char *n_name; /* for use when in-core */ long n_strx; /* index into file string table */ } n_un; unsigned char n_type; /* type flag */ char n_sect; /* section number or NO_SECT */ short n_desc; /* see struct desc, below */ unsigned n_value; /* address or offset or line */ }; The low bits of the n_type field are used for the symbol type, according to the following masks, defined in <nlist.h>. A symbol can be of none these types by having none of these bits set. /* * Simple values for n_type. */ #define N_UNDF 0x0 /* undefined */ #define N_ABS 0x2 /* absolute */ #define N_SECT 0xe /* defined in section number n_sect */ #define N_EXT 01 /* external bit, or'ed in */ The n_value field of a symbol is relocated by the linker, ld(1) as an address within the appropriate section for N_SECT types based on the. N_value fields of symbols not in any segment are unchanged by the linker. In addition, the linker will discard certain symbols, according to rules of its own, unless the n_type field has one of the following bits set: /* * Other permanent symbol table entries have some of the N_STAB bits set. * These are given in <stab.h> */ #define N_STAB 0xe0 /* if any of these bits set, don't discard */ This allows up to 112 (7 * 16) symbol types, split between the various symbol types. Some of these have already been claimed. The old sym- bolic debugger, sdb, uses the following n_type values: #define N_GSYM 0x20 /* global symbol: name,,NO_SECT,type,0 */ #define N_FNAME 0x22 /* procedure name (f77 kludge): name,,NO_SECT */ #define N_FUN 0x24 /* procedure: name,,n_sect,linenumber,address */ #define N_STSYM 0x26 /* static symbol: name,,n_sect,type,address */ #define N_LCSYM 0x28 /* .lcomm symbol: name,,n_sect,type,address */ #define N_BNSYM 0x2e /* begin nsect sym: 0,,n_sect,0,address */ #define N_RSYM 0x40 /* register sym: name,,NO_SECT,type,register */ #define N_SLINE 0x44 /* src line: 0,,n_sect,linenumber,address */ #define N_ENSYM 0x4e /* end nsect sym: 0,,n_sect,0,address */ #define N_SSYM 0x60 /* structure elt: name,,NO_SECT,type,struct_offset */ #define N_SO 0x64 /* source file name: name,,n_sect,0,address */ #define N_LSYM 0x80 /* local sym: name,,NO_SECT,type,offset */ #define N_BINCL 0x82 /* include file beginning: name,,NO_SECT,0,sum */ #define N_SOL 0x84 /* #included file name: name,,n_sect,0,address */ #define N_PSYM 0xa0 /* parameter: name,,NO_SECT,type,offset */ #define N_EINCL 0xa2 /* include file end: name,,NO_SECT,0,0 */ #define N_ENTRY 0xa4 /* alternate entry: name,,n_sect,linenumber,address */ #define N_LBRAC 0xc0 /* left bracket: 0,,NO_SECT,nesting level,address */ #define N_EXCL 0xc2 /* deleted include file: name,,NO_SECT,0,sum */ #define N_RBRAC 0xe0 /* right bracket: 0,,NO_SECT,nesting level,address */ #define N_BCOMM 0xe2 /* begin common: name,,NO_SECT,0,0 */ #define N_ECOMM 0xe4 /* end common: name,,n_sect,0,0 */ #define N_ECOML 0xe8 /* end common (local name): 0,,n_sect_,0,address */ #define N_LENG 0xfe /* second stab entry with length information */ where the comments give sdb conventional use for .stab s and the n_name, n_sect, n_desc, and n_value fields of the given n_type. Sdb uses the n_desc field to hold a type specifier in the form used by the Portable C Compiler, cc(1); see the header file pcc.h for details on the format of these type values. The Berkeley Pascal compiler, pc(1), uses the following n_type value: #define N_PC 0x30 /* global pascal symbol: name,,NO_SECT,subtype,line */ and uses the following subtypes to do type checking across separately compiled files: 1 source file name 2 included file name 3 global label 4 global constant 5 global type 6 global variable 7 global function 8 global procedure 9 external function 10 external procedure 11 library variable 12 library routine SEE ALSO
as(1), ld(1), dbx(1), Mach-O(5) BUGS
More basic types are needed. HISTORY
The stab file appeared in 4.0BSD. Darwin November 16, 2001 Darwin
All times are GMT -4. The time now is 11:42 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy