| delorie.com/archives/browse.cgi | search |
| From: | "Mark E." <snowball3 AT bigfoot DOT com> |
| To: | djgpp-workers AT delorie DOT com |
| Date: | Wed, 22 Aug 2001 13:59:40 -0400 |
| MIME-Version: | 1.0 |
| Subject: | Re: rhgdb and dwarf2 oddity |
| Message-ID: | <3B83BACC.6705.A2BE59@localhost> |
| In-reply-to: | <5137-Wed22Aug2001184244+0300-eliz@is.elta.co.il> |
| References: | <3B837ED5 DOT 9470 DOT 9EB9A AT localhost> (snowball3 AT bigfoot DOT com) |
| X-mailer: | Pegasus Mail for Win32 (v3.12c) |
| 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 |
> the debuggee. If so, the equivalent sequence in GDB would be to let > the program run to completion, then type "run" again. This restarts > the program with the same argv[] array as before, and the breakpoints > you've set should still be valid. I did this and gdb had no complaint. > Perhaps a fixed release of Binutils could be available by the time > GDB 5.1 is out. (I estimate that will take at least another month.) Sure. Mark
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |