Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: matthew green <mrg@cygnus.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: re: [patch]: 2 more needed changes for sim-fpu.c & psim
Date: Fri, 14 Dec 2001 20:17:00 -0000	[thread overview]
Message-ID: <7.1008389753@cygnus.com> (raw)
In-Reply-To: your message of "Fri, 14 Dec 2001 11:44:13 -0800." <3C1A568D.3020300@cygnus.com>


   
   I'm puzzled by some of the includes.  Well "defs.h" to be honest.   I 
   know the PPC has a nasty hack so that it can access the GDB register 
   names but I'm not sure that main.c - a standalone program - should 
   include "defs.h".

main.c doesn't need defs.h, right.
   
   I think the error stuff should go to stderr.

hmm, i choose stdout because the "error" function a couple of pages
above does the same...
   
   From memory, for the sim_call.c, the error stuff should go to the callback.

OK, i've done this..  how's this?



	* main.c: Include "bfd.h", "callback.h" and "remote-sim.h".
	(sim_io_error): New function.
	* sim_calls.c: (sim_io_error): New function.


Index: sim_calls.c
===================================================================
RCS file: /cvs/src/src/sim/ppc/sim_calls.c,v
retrieving revision 1.2
diff -p -r1.2 sim_calls.c
*** sim_calls.c	2000/12/08 01:52:41	1.2
--- sim_calls.c	2001/12/15 04:14:35
*************** sim_io_flush_stdoutput(void)
*** 441,446 ****
--- 441,456 ----
    }
  }
  
+ void
+ sim_io_error (SIM_DESC sd, const char *fmt, ...)
+ {
+   va_list ap;
+   va_start(ap, fmt);
+   callbacks->evprintf_filtered (callbacks, fmt, ap);
+   va_end(ap);
+   callbacks->error (callbacks, "");
+ }
+ 
  /****/
  
  void *
Index: main.c
===================================================================
RCS file: /cvs/src/src/sim/ppc/main.c,v
retrieving revision 1.1.1.1
diff -p -r1.1.1.1 main.c
*** main.c	1999/04/16 01:35:11	1.1.1.1
--- main.c	2001/12/15 04:14:35
***************
*** 30,35 ****
--- 30,39 ----
  #include "device.h" /* FIXME: psim should provide the interface */
  #include "events.h" /* FIXME: psim should provide the interface */
  
+ #include "bfd.h"
+ #include "callback.h"
+ #include "remote-sim.h"
+ 
  #ifdef HAVE_STDLIB_H
  #include <stdlib.h>
  #endif
*************** sim_io_flush_stdoutput(void)
*** 220,225 ****
--- 224,245 ----
      error("sim_io_flush_stdoutput: invalid switch\n");
      break;
    }
+ }
+ 
+ void
+ sim_io_error (SIM_DESC sd, const char *msg, ...)
+ {
+   va_list ap;
+   va_start(ap, msg);
+   vprintf(msg, ap);
+   printf("\n");
+   va_end(ap);
+ 
+   /* any final clean up */
+   if (ppc_trace[trace_print_info] && simulation != NULL)
+     psim_print_info (simulation, ppc_trace[trace_print_info]);
+ 
+   exit (1);
  }
  
  


  reply	other threads:[~2001-12-15  4:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-13 17:30 matthew green
2001-12-14 14:41 ` Andrew Cagney
2001-12-14 20:17   ` matthew green [this message]
2001-12-14 21:01     ` Andrew Cagney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7.1008389753@cygnus.com \
    --to=mrg@cygnus.com \
    --cc=ac131313@cygnus.com \
    --cc=gdb-patches@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox