Assuming you got the load address correct, and the data at the globals look
correct it should just work.
Google/Bing gdb tutorial
You should be able to run the backtrace command and see the stack frame. You
can only see locals for the frame that your are currently in, assuming the
compiler has not optimized the value into a register.
The only difference between remote and local debugging with gdb is you don't
use the file and run commands, and for EFI you use add-symbol-file to get
symbols loaded. Note you need to add-symbol-file for every module to get full
source level debug.
Andrew Fish
On Jul 20, 2012, at 6:24 AM, Satheesh B R wrote:
>
> Hi Andrew,
>
> Even on using 'add-symbol-file' command I am just able to get the
> values of global variables. What should be done for inserting breakpoints,
> printing local variables etc .. Could you please guide me.
>
> Thanks and Regards
> Satheesh.B.R
>
> >Message: 3
> >Date: Thu, 19 Jul 2012 09:33:37 -0700
> >From: Andrew Fish <[email protected]>
> >Subject: Re: [edk2] Reg : : GDB for ARM
> >To: [email protected]
> >Message-ID: <[email protected]>
> >Content-Type: text/plain; charset="us-ascii"
>
> >I think you want to use the add-symbol-file command. This loads symbols. The
> >file command tries to load an executable and run it, I don't >think that
> >works across the remote connection.
>
> >Andrew Fish
>
>
>
>
>
> >On Jul 18, 2012, at 11:42 PM, Satheesh B R wrote:
>
> > Hi All
> >
> > I am trying to debug the DXE driver remotely. I use X-86 GDB of
> > my host machine(Ubuntu) to debug the target(BeagleBoard Rev C4)
> > connected by serial port.
> >
> > I have done the following :
> >
> > Connect the host and target using serial cable.
> >
> > Booting to the shell in the target machine(GdbStub has been added in
> > the boot file).
> >
> > In host establishing the connection by command "target remote
> > /dev/ttyUSB0" in gdb.
> >
> > "cd" to the directory where the 'dll' of DXE driver present.
> >
> > Adding symbol file using the command "file DRIVER_NAME.dll "
> >
> > Now on giving the "run" command I get
> >
> > <workroot>/DRIVER_NAME.dll : cannot execute binary file
> > <workroot>/DRIVER_NAME.dll : Success
> > During startup program exited with code 126.
> >
> > Am I following the correct procedure.Please help me with the same.
> >
> > Thanks and Regards
> > Satheesh.B.R
>
>
>
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
edk2-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/edk2-devel
