X-Authentication-Warning: acp3bf.physik.rwth-aachen.de: broeker owned process doing -bs Date: Tue, 31 Jul 2001 10:58:38 +0200 (MET DST) From: Hans-Bernhard Broeker X-Sender: broeker AT acp3bf To: djgpp-workers AT delorie DOT com cc: n_abing AT ns DOT roxas-online DOT net DOT ph Subject: Re: DJGPP core dumper In-Reply-To: <200107281642.MAA23764@delorie.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Reply-To: djgpp-workers AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Sat, 28 Jul 2001, Eli Zaretskii wrote: > Finally, I'm not sure what to do with the environment and backtrace > sections: GDB doesn't use them. But maybe the special coredump-interpreting program that came with that package does? > Btw, does anyone know what is the core_command member of elf_tdata > structure (see bfd/elf.c in Binutils or in GDB) used for, and what > should it hold? That's one I may be able help with. The usage/calling sequence for this is: bfd_core_file_failing_command (bfd/corefile.c) | +->{elf,...}_core_file_failing_command (bfd/elfcore.h) | +->reads: core_command bfd_core_file_failing_command is even documented a bit by comments in the sources. It's called by display_bfd() in binutils/size.c. The struct field is written to by elfcore_grok_psinfo (bfd/elf.c) by copying it out of the 'ps info' structure. In short: yes, this is argv[], if available. [Cscope is really a nice tool for digging up stuff like this...] -- Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de) Even if all the snow were burnt, ashes would remain.