store the contents of target’s RAM in frequent intervals

Hi,
             I would like to know if there is any possibility for adding
functionality in GDB which could store the contents of target’s RAM in
frequent intervals so that, when accidentally switched off or shut down of
an embedded target, we can resume the execution of the program from where it
earlier stopped (i.e previous save point). Conceptually It is somewhat
similar to the Hibernate function used in Windows xp, Service pack 2. I was
thinking of inducing this functionality for embedded targets in particular.  
             Need comes for test cases which runs for days, or even weeks.
Suppose, on 2nd day of program run, somebody switches it off, it should be
able to resume from that location after it's switched on. 
Thanks. 
Reg, 
Sandeep
--

-- 
View this message in context: http://www.nabble.com/store-the-contents-of-target%E2%80%99s-RAM-in-frequent-intervals-tp20848914p20848914.html
Sent from the Gnu - gdb - General mailing list archive at Nabble.com.

HELP with MACINTEL

If i use a mac ppc and gdb
i attach gdb to an app and i can read the instruction in assembler like :

0x1214a14c <_ZN5Tools4OpenEm+96>:       bl      0x12168494
<_ZN7CF_Wibu7OpenBoxEu7__bool8ll>[/b]
0x1214a150 <_ZN5Tools4OpenEm+100>:      cmpwi   r3,0
0x1214a154 <_ZN5Tools4OpenEm+104>:      beq-    0x1214a160
<_ZN5Tools4OpenEm+116>

then with gdb i can find the corrispodent in hexa

0x1214a14c <_ZN5Tools4OpenEm+96>:       0x4801e349[/b]      0x2c030000     
0x4182000c   

using then resourcere app i can find hexa inside the original appicatil 
with this procedire using a mac PPC  i find the HEXA code

NOW the question is
with MACINTEL what change
the same procedure dont work

please help
--

-- 
View this message in context: http://www.nabble.com/HELP-with-MACINTEL-tp20955788p20955788.html
Sent from the Gnu - gdb - General mailing list archive at Nabble.com.

Target Description for ARM

Hi,

I am   new to GDB environment. Currently i configured GDB for  ARM. I have a
target (simulator) for ARM 9 and a custom coprocessor . I have connected my
target with gdb using gdbserver ( target remote) , and it is working fine as
, i can see my target registers (r0 -r15, cpsr etc.). Now i want add the
target co processor (ARM's) registers to the gdb target description, so that
i can view my extra registers too. Could any one  help me on this  , to
describe what are the steps for  adding new registers  to gdb ARM target.

thanks in advance
--

-- 
View this message in context: http://www.nabble.com/Target--Description-for-ARM-tp21013849p21013849.html
Sent from the Gnu - gdb - General mailing list archive at Nabble.com.

Target Description for ARM

Hi all,

I am   new to GDB environment. Currently i configured GDB for  ARM. I have a
target (simulator) for ARM 9 and a custom coprocessor . I have connected my
target with gdb using gdbserver ( target remote) , and it is working fine as
, i can see my target registers (r0 -r15, cpsr etc.). Now i want add the
target co processor (ARM's) registers to the gdb target description, so that
i can view my extra registers too. Could any one  help me on this  , to
describe what are the steps for  adding new registers  to gdb ARM target.

Thanks in advance
Thejes
--

-- 
View this message in context: http://www.nabble.com/Target--Description-for-ARM-tp21013857p21013857.html
Sent from the Gnu - gdb - General mailing list archive at Nabble.com.

read local variables

Keep the breakpoint instead of line numbers?

Hi all

I am new this debugger. I need any one to reply immediately for my query.

I need your help. Is it possible in GDB debbugger keeping the BreakPoint(BP)
instead of line numbers in the source file. Because for me source code keep
on changing. Any other way to solve the issue.

Clarification:
is it possible in debugger keeping the BP in particlur if condition or
string 
e.g
1.  void main()
2.  {
3.  int i=0;
4.  printf i;
5. }
For the above case i need to keep the BP at (i=0;) without the help of line
number. we need to search that line and should keep the break point?
--

-- 
View this message in context: http://www.nabble.com/Keep-the-breakpoint-instead-of-line-numbers--tp21074515p21074515.html
Sent from the Gnu - gdb - General mailing list archive at Nabble.com.

SIGTRAP problem

Hi all,

i am working with codeblocks and GNU gdb 6.7.50.20071127 under windows.

When i start to debug my program, i am receiving:

signal SIGTRAP, Trace/breakpoint trap.
In ntdll!DbgUiIssueRemoteBreakin () (C:\WINDOWS\system32\ntdll.dll)

So it come from ntdll.
Is there a way to ignore this trap, so i can go on debugging ?

thanks,

--

-- 
View this message in context: http://www.nabble.com/SIGTRAP-problem-tp21167280p21167280.html
Sent from the Gnu - gdb - General mailing list archive at Nabble.com.