Article View: gnu.gdb.bug
Article #764Re: Gdb reading of symbols
From: Chris Benenati
Date: Tue, 18 Apr 1989 22:40
Date: Tue, 18 Apr 1989 22:40
11 lines
1123 bytes
1123 bytes
In article <8904180616.AA13236@gilroy.pa.dec.com> bothner@WSL.DEC.COM writes: >I am not a naive user. I have ported gdb to a very different >platform (the V operating system - messages and no ptrace). >In spite of this, I thought the slow-ness of next was because it >was broken. Are you sure its the symbol reading that's taking the time? If your "very different platform" happens to involve a target remote system over a serial line, performing a C-level "next" can take a LONG time because gdb will start, stop, and read/write registers to/from the target after EVERY machine instruction.
Technical Details
Message-ID:
<4322@omepd.UUCP>Path:
arc1-ca.pugleaf.net!utzoo!telly!attcan!uunet!tut.cis.ohio-state.edu!rutgers!apple!oliveb!intelca!mipos3!omepd!mipon2!chrisbReferences:
<8904172206.AA19123@rice-chex.ai.mit.edu> <8904180616.AA13236@gilroy.pa.dec.com>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!telly!attcan!uunet!tut.cis.ohio-state.edu!rutgers!apple!oliveb!intelca!mipos3!omepd!mipon2!chrisb From: chrisb@mipon2.intel.com (Chris Benenati) Newsgroups: gnu.gdb.bug Subject: Re: Gdb reading of symbols Message-ID: <4322@omepd.UUCP> Date: 18 Apr 89 22:40:36 GMT References: <8904172206.AA19123@rice-chex.ai.mit.edu> <8904180616.AA13236@gilroy.pa.dec.com> Sender: news@omepd.UUCP Reply-To: chrisb@mipon2.UUCP (Chris Benenati) Distribution: gnu Organization: Intel Corp., Hillsboro Lines: 11