|Subject:||Help in remote testing of custom debugger.|
|Date:||Mon, 16 Jul 2007 11:00:23 +0530|
I am testing a custom build debugger on command line interface using dejagnu testsuite.
In the normal way, in order to debug the application, I’ll first run the executable on the simulator specifying the configuration and port (say, 4000) to connect. This application now runs waiting for a remote debugger to attach to itself and waits.
Then, in another command window, I run the customized debugger specifying the executable file. I then connect to the already running process by the command:
target extended-remote localhost:4000 (where 4000 is the port specified earlier).
Then, I can continue to debug the application in the normal way.
My question is, I have to get this setup running on dejagnu gdb testsuite. Can anyone help me in setting the configuration?. How do I need to setup the testsuite to get it running in the above setup?
Note: The target hardware to run the executable is not x86. I’m using a customized c compiler and also a customized debugger (which is ported from gdb).
Thanks in advance,
E-mail may contain viruses. Before opening attachments please check them for viruses and defects. While MindTree Consulting Limited (MindTree) has put in place checks to minimize the risks, MindTree will not be responsible for any viruses or defects or any forwarded attachments emanating either from within MindTree or outside.
Please note that e-mails are susceptible to change and MindTree shall not be liable for any improper, untimely or incomplete transmission.
MindTree reserves the right to monitor and review the content of all messages sent to or from MindTree e-mail address. Messages sent to or from this e-mail address may be stored on the MindTree e-mail system or else where.
|[Prev in Thread]||Current Thread||[Next in Thread]|