|
Re: Memory and register changing [message #48925 is a reply to message #48866] |
Tue, 05 November 2002 16:23 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) ![Go to next message Go to next message](theme/Solstice/images/down.png) |
Eclipse User![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=) |
|
|
|
Originally posted by: mikhailk.qnx.com
The problem with registers is a bug. I have submitted a bug for it (25730).
To change memory you have to type the values and then press the 'Save
changes' button.
This works only for hexadecimal format.
Mikhail Khodjaiants
"Igor S. Zamyatin" <isz@interstron.ru> wrote in message
news:aq88ql$o9u$1@rogue.oti.com...
>
>
> Hi all!
>
> I downloaded new CDT packages from CVS in order to use new Memory and
> Registers view. But I didn't manage to change memory from Memory View(I
> just didn't find how to do it) and I didn't manage to change register
> values: after I've changed a value of some register(using right mouse
> click) an old one appeared again.
>
> May be someone prompt what's the problem is?
>
> Thanks,
> Igor S. Zamyatin
>
> Interstron Ltd.
>
|
|
|
Re: Memory and register changing [message #48953 is a reply to message #48925] |
Tue, 05 November 2002 16:36 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) ![Go to next message Go to next message](theme/Solstice/images/down.png) |
Eclipse User![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=) |
|
|
|
Originally posted by: mikhailk.qnx.com
"Mikhail Khodjaiants" <mikhailk@qnx.com> wrote in message
news:aq8pag$2k9$1@rogue.oti.com...
> The problem with registers is a bug. I have submitted a bug for it
(25730).
Fixed.
> To change memory you have to type the values and then press the 'Save
> changes' button.
> This works only for hexadecimal format.
>
> Mikhail Khodjaiants
>
> "Igor S. Zamyatin" <isz@interstron.ru> wrote in message
> news:aq88ql$o9u$1@rogue.oti.com...
> >
> >
> > Hi all!
> >
> > I downloaded new CDT packages from CVS in order to use new Memory and
> > Registers view. But I didn't manage to change memory from Memory View(I
> > just didn't find how to do it) and I didn't manage to change register
> > values: after I've changed a value of some register(using right mouse
> > click) an old one appeared again.
> >
> > May be someone prompt what's the problem is?
> >
> > Thanks,
> > Igor S. Zamyatin
> >
> > Interstron Ltd.
> >
>
>
|
|
|
|
Re: Memory and register changing [message #49062 is a reply to message #49001] |
Wed, 06 November 2002 15:40 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) |
Eclipse User![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=) |
|
|
|
Originally posted by: mikhailk.qnx.com
"Igor S. Zamyatin" <isz@interstron.ru> wrote in message
news:aqaeaj$s8l$1@rogue.oti.com...
> Mikhail Khodjaiants wrote:
>
> > The problem with registers is a bug. I have submitted a bug for it
(25730).
> > To change memory you have to type the values and then press the 'Save
> > changes' button.
>
> Could you please specify more exactly what should I put into "Address"
> memo in Memory View before pressing "Save changes" button because I'm
> typing "0x0 5", then pressing that button and nothing happenning.
>
To view a memory block you have to an expression into 'Address' field and
press Enter. It could a direct address or a correct 'C/C++' expression. For
example, '&x' where 'x' is a local variable in the current context. The size
of block is hardcoded for now but it will probably be added to the
preferences of the Memory view.
As soon as have a memory block in your view you can change the format, unit
size and number of columns and switch on/off the ascii presentation.
The 'Refresh' button updates the memory block. If you want the memory block
to be automatically updated at every step of your debug session switch on
the 'Auto-Refresh' button.
To modify your memory block just type the values and press the 'Save
Changes' button.
> And another one. I've noticed that when I want to look at register
> values Debugger had posted to gdb following commands
>
> 29-data-list-register-values x 0
>
> 30-data-list-register-values x 0
>
> 31-data-list-register-values x 0
>
> 32-data-list-register-values x 1
>
> 33-data-list-register-values x 1
>
> 34-data-list-register-values x 1
>
> 35-data-list-register-values x 2
>
> 36-data-list-register-values x 2
>
> 37-data-list-register-values x 2
>
> 38-data-list-register-values x 3
>
> 39-data-list-register-values x 3
>
> 40-data-list-register-values x 3
>
> 41-data-list-register-values x 4
>
> 42-data-list-register-values x 4
>
> 43-data-list-register-values x 4
>
> 44-data-list-register-values x 5
>
> 45-data-list-register-values x 5
>
> 46-data-list-register-values x 5
>
> 47-data-list-register-values x 6
>
> 48-data-list-register-values x 6
>
> 49-data-list-register-values x 6
>
> 50-data-list-register-values x 7
>
> 51-data-list-register-values x 7
>
> 52-data-list-register-values x 7
>
> 53-data-list-register-values x 8
>
> 54-data-list-register-values x 8
>
> 55-data-list-register-values x 8
>
> 56-data-list-register-values x 9
>
> 57-data-list-register-values x 9
>
> 58-data-list-register-values x 9
>
> 59-data-list-register-values x 10
>
> 60-data-list-register-values x 10
>
> 61-data-list-register-values x 10
>
> 62-data-list-register-values x 11
>
> 63-data-list-register-values x 11
>
> 64-data-list-register-values x 11
>
> 65-data-list-register-values x 12
>
> 66-data-list-register-values x 12
>
> 67-data-list-register-values x 12
>
> 68-data-list-register-values x 13
>
> 69-data-list-register-values x 13
>
> 70-data-list-register-values x 13
>
> 71-data-list-register-values x 14
>
> 72-data-list-register-values x 14
>
> 73-data-list-register-values x 14
>
> 74-data-list-register-values x 15
>
> 75-data-list-register-values x 15
>
> 76-data-list-register-values x 15
>
> 77-data-list-register-values x 16
>
> 78-data-list-register-values x 16
>
> 79-data-list-register-values x 16
>
> 80-data-list-register-values x 17
>
> 81-data-list-register-values x 17
>
> 82-data-list-register-values x 17
>
> 83-data-list-register-values x 18
>
> 84-data-list-register-values x 18
>
> 85-data-list-register-values x 18
>
> 86-data-list-register-values x 19
>
> 87-data-list-register-values x 19
>
> 88-data-list-register-values x 19
>
> 89-data-list-register-values x 20
>
> 90-data-list-register-values x 20
>
> 91-data-list-register-values x 20
>
> 92-data-list-register-values x 21
>
> 93-data-list-register-values x 21
>
> 94-data-list-register-values x 21
>
> 95-data-list-register-values x 22
>
> 96-data-list-register-values x 22
>
> 97-data-list-register-values x 22
>
> 98-data-list-register-values x 23
>
> 99-data-list-register-values x 23
>
> 100-data-list-register-values x 23
>
> 101-data-list-register-values x 24
>
> 102-data-list-register-values x 24
>
> 103-data-list-register-values x 24
>
> 104-data-list-register-values x 25
>
> 105-data-list-register-values x 25
>
> 106-data-list-register-values x 25
>
> 107-data-list-register-values x 26
>
> 108-data-list-register-values x 26
>
> 109-data-list-register-values x 26
>
> 110-data-list-register-values x 27
>
> 111-data-list-register-values x 27
>
> 112-data-list-register-values x 27
>
> 113-data-list-register-values x 28
>
> 114-data-list-register-values x 28
>
> 115-data-list-register-values x 28
>
> 116-data-list-register-values x 29
>
> 117-data-list-register-values x 29
>
> 118-data-list-register-values x 29
>
> 119-data-list-register-values x 30
>
> 120-data-list-register-values x 30
>
> 121-data-list-register-values x 30
>
> 122-data-list-register-values x 31
>
> 123-data-list-register-values x 31
>
> 124-data-list-register-values x 31
>
> Is it important to post 3 equal commands?
>
I will look at it.
> Thanks
>
> Igor S. Zamyatin
>
Thank you,
Mikhail Khodjaiants
>
>
> > This works only for hexadecimal format.
>
> > Mikhail Khodjaiants
>
> > "Igor S. Zamyatin" <isz@interstron.ru> wrote in message
> > news:aq88ql$o9u$1@rogue.oti.com...
> > >
> > >
> > > Hi all!
> > >
> > > I downloaded new CDT packages from CVS in order to use new Memory and
> > > Registers view. But I didn't manage to change memory from Memory
View(I
> > > just didn't find how to do it) and I didn't manage to change register
> > > values: after I've changed a value of some register(using right mouse
> > > click) an old one appeared again.
> > >
> > > May be someone prompt what's the problem is?
> > >
> > > Thanks,
> > > Igor S. Zamyatin
> > >
> > > Interstron Ltd.
> > >
>
>
>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.04031 seconds