RE: [RFC] New GDB Port CR16

[Kaushik Phatak <Kaushik.Phatak@kpitcummins.com>]

>> so the fix would be to change this file to include the header.

Yes, I agree. I have added the prototypes to the header file and the patch below
should fix this issue,

include/opcode/ChangeLog:
	* cr16.h: Add prototypes for cr16-dis.c

	
--- ./gdb_src.orig/include/opcode/cr16.h        2010-04-15 15:56:09.000000000 +0530
+++ ./gdb_src/include/opcode/cr16.h     2012-09-12 10:44:09.000000000 +0530
@@ -435,4 +435,8 @@ extern const inst *instruction;
 typedef long long int LONGLONG;
 typedef unsigned long long ULONGLONG;

+/* Prototypes for function in cr16-dis.c  */
+void make_instruction (void);
+int match_opcode (void);
+
 #endif /* _CR16_H_ */


Additionally, I was working on couple of issues as mentioned in the post below,
http://sourceware.org/ml/gdb-patches/2012-09/msg00152.html
Issue 1 is sorted out by migrating my gdbserver sources to the latest 7.5 release
version. I was earlier working on a much older branch and had only migrated the
host side gdb to 7.5.

Issue 2 is related to the -fPIC option which causes my global data to be placed
at an offset causing the host side gdb to query incorrect addresses for global
variables. Any comments on my proposed patch/hack ?
http://sourceware.org/ml/gdb-patches/2012-09/msg00152/gdb_core_fpic_suspect.diff

Thanks & Best Regards,
Kaushik Phatak