summaryrefslogtreecommitdiffstats
path: root/c/src/librdbg/src/awk.svc (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Patch rtems-rc-20000104-17.diff from Ralf Corsepius <corsepiu@faw.uni-ulm.de>Joel Sherrill2000-01-131-2/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | that addresses the librdbg/rpcgen related problems: Changes: * All rpcgen generated files are now kept inside of the source tree * Fix librdbg/configure to correctly detect presence of rpcgen and awk * Use rpcgen -m to generated remdeb_svc.c * Remove msgout/_msgout from awk.svc * minor cleanups to librdbg/configure.in ATTENTION --- IMPORTANT: * With keeping rpc-generated files pre-build inside of the source tree, you as the packager of RTEMS have to ensure that timestamps are correctly set up: The generated files must not be older than the *.x files. * This is extraordinarily important when - putting the package on read-only media - after checking out from CVS - after modifications to the *.x files * If one of the *.x files is modified you have to either - build for i386/pc386 and powerpc/mcp750 - or to invoke the same rpcgen calls as the librdbg/src/<cpu>/<bsp>/Makefile.am do manually before checking-in the files to CVS. Proposal: We could add something to bootstrap for touching the rpcgen-generated sources and/or to manually regenerate them. NOTE FROM JOEL: Ralf proposed modifying bootstrap to handle rpcgen. I think this is the best solution as it is something already done in the snapshot procedure.
* Patch from Eric Valette <valette@crf.canon.fr> and Emmanuel RaguetJoel Sherrill1999-08-101-1/+3
| | | | | | | | | | | | <raguet@crf.canon.fr>: - the dec21140 driver code has been hardened (various bug fixed) Emmanuel, - bug in the mcp750 init code have been fixed (interrupt stack/initial stack initialization), BSS correctly cleared (Eric V) - remote debugging over TCP/IP is nearly complete (berakpoints, backtrace, variables,...) (Eric V), - exception handling code has also been improved in order to fully support RDBG requirements (Eric V),
* Patch from Emmanuel Raguet <raguet@crf.canon.fr> to add remote debug serverJoel Sherrill1998-12-031-0/+65
and RPC support to RTEMS. Thanks. :) Email follows: Hello, For Xmas, here is the Remote Debugger on RTEMS ! Here are 2 patches for the Remote Debugger on RTEMS for pc386 from Linux host : - one for RTEMS it self, - one for GDB-4.17. 1/ RTEMS patch -------------- This patch adds 2 libraries : - a simplified SUN RPC library - the Remote Debugger library The configuration command is the following : ../rtems4/configure --target=i386-rtemself --enable-rtemsbsp=pc386 --enable-rdbg The SUN RPC library is built only if networking is set. The RDBG library is built if networking and enable-rdbg are set. The function used to initialize the debugger is : rtems_rdbg_initialize (); A special function has been created to force a task to be in a "debug" state : enterRdbg(). The use of this function is not mandatory. 2/ GDB-4.17 patch ----------------- This patch create a new RTEMS target for GDB-4.17. The configuration command is the following : ./configure --enable-shared --target=i386RTEMS To connect to a target, use : target rtems [your_site_address] Then, attach the target using : attach 1 And... Debug ;) You can obtain the original GDB-4.17 on ftp://ftp.debian.org/debian/dists/stable/main/source/devel/gdb_4.17.orig.tar.gz This has been tested from a Debian 2.0.1 linux host.