Article View: gnu.gcc.help
Article #53445Re: GCC/GDB Debugging Information
From: Wolfgang Seelbach
Date: Wed, 29 Jan 1992 08:38
Date: Wed, 29 Jan 1992 08:38
19 lines
1612 bytes
1612 bytes
In article <knklhfINNilr@agate.berkeley.edu>, rwahbe@madrone.CS.Berkeley.EDU (Robert Wahbe) writes: > Does anyone know of an up-to-date definition of the > debugging information generated by gcc and used by gdb and dbx. I don`t now such a definition (but looking for it too)! > The C compiler that is shipped with SunOS 4.1 produces > slightly different information. Is there a theoretical standard? We use SunOS 4.1 (Sparc) and gcc (1.40). If you want to use dbxtool (dbx), you have to change and recompile gcc.c: in function "process_command(argc, argv)" all "input-file-names (infiles[..])" and "output-file-names (-o <..>)" should be extended to full path names via the "realpath" system call (for output-files the error ENOENT has to be ignored). Without this modification, the debugger will not be able to find the sources if your current working directory does not contain the source files of the program to debug. W. Seelbach (seelbach@fernuni-hagen.de, seelbach@dhafeu61.bitnet)
Technical Details
Message-ID:
<7637@fuhainf.fernuni-hagen.de>Path:
arc1-ca.pugleaf.net!sparky!uunet!mcsun!unido!fuhainf!lorien!seelbachReferences:
<knklhfINNilr@agate.berkeley.edu>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 11318c,e5843ad496dbb2cf X-Google-Attributes: gid11318c,public X-Google-ArrivalTime: 1992-01-29 09:13:29 PST Path: arc1-ca.pugleaf.net!sparky!uunet!mcsun!unido!fuhainf!lorien!seelbach From: seelbach@lorien.fernuni-hagen.de (Wolfgang Seelbach) Newsgroups: gnu.gcc.help Subject: Re: GCC/GDB Debugging Information Keywords: debugg, stab Message-ID: <7637@fuhainf.fernuni-hagen.de> Date: 29 Jan 92 08:38:54 GMT References: <knklhfINNilr@agate.berkeley.edu> Sender: news@fuhainf.fernuni-hagen.de Organization: FernUniversitaet Hagen, Germany Lines: 19