aboutsummaryrefslogtreecommitdiff
path: root/gdb
diff options
context:
space:
mode:
authorJim Blandy <jimb@codesourcery.com>2001-09-13 18:53:42 +0000
committerJim Blandy <jimb@codesourcery.com>2001-09-13 18:53:42 +0000
commitfe4900853add504e75e71e2a3d8cc5ce75f5b4f2 (patch)
treecf2f62b6da2748a955a078fcb8499b93267a121a /gdb
parent348d75a52ff8e3fa2cb16a82efd88a0ca2e866bc (diff)
downloadgdb-fe4900853add504e75e71e2a3d8cc5ce75f5b4f2.zip
gdb-fe4900853add504e75e71e2a3d8cc5ce75f5b4f2.tar.gz
gdb-fe4900853add504e75e71e2a3d8cc5ce75f5b4f2.tar.bz2
(monitor_load): Fix indentation.
Diffstat (limited to 'gdb')
-rw-r--r--gdb/monitor.c15
1 files changed, 7 insertions, 8 deletions
diff --git a/gdb/monitor.c b/gdb/monitor.c
index d1a48f2..0603806 100644
--- a/gdb/monitor.c
+++ b/gdb/monitor.c
@@ -2202,19 +2202,18 @@ monitor_load (char *file, int from_tty)
monitor_expect_prompt (NULL, 0);
}
-/* Finally, make the PC point at the start address */
-
+ /* Finally, make the PC point at the start address */
if (exec_bfd)
write_pc (bfd_get_start_address (exec_bfd));
inferior_ptid = null_ptid ; /* No process now */
-/* This is necessary because many things were based on the PC at the time that
- we attached to the monitor, which is no longer valid now that we have loaded
- new code (and just changed the PC). Another way to do this might be to call
- normal_stop, except that the stack may not be valid, and things would get
- horribly confused... */
-
+ /* This is necessary because many things were based on the PC at the
+ time that we attached to the monitor, which is no longer valid
+ now that we have loaded new code (and just changed the PC).
+ Another way to do this might be to call normal_stop, except that
+ the stack may not be valid, and things would get horribly
+ confused... */
clear_symtab_users ();
}