ChangeLog info missing ?

ChangeLog info missing ?

[paawan oza]

Hi Michael,

I have downloaded gdb 7.2 to continue working on reversible debugging. As I have 
observed the ChangeLog, there are 2 things.

1) below flaoting point changelog is missing from ChangeLog of gdb

--- gdb.orig/ChangeLog    2009-08-21 21:37:18.000000000 -0400
+++ gdb.new/floating.ChangeLog    2009-08-21 21:37:13.000000000 -0400
@@ -1,3 +1,9 @@
+2009-08-21  Oza Pawandeep  <paawan1982@yahoo.com>
+
+        * i386-tdep.c:  Support for floating point recording.
+        Records and Replay the i386 floating point registers,
+        of i387 FPU.
+
 2009-08-19  Ralf Wildenhues  <Ralf.Wildenhues@gmx.de>
 
     * configure.ac: Call AC_DISABLE_OPTION_CHECKING.


2) there has been work done on arm-tdep.c as I see ChangeLog 
(as I was also paralelly working, but I was not sure about already work going 
on)
The progress was slow because I changed organisation : (

I am not sure how much work has been done on arm and what is left..

kindly clarify my understanding on point 1 and possibly on point 2.

Regards,
Oza.


      

Re: ChangeLog info missing ?

[Michael Snyder]

paawan oza wrote:
> Hi Michael,
> 
> I have downloaded gdb 7.2 to continue working on reversible debugging. As I have 
> observed the ChangeLog, there are 2 things.
> 
> 1) below flaoting point changelog is missing from ChangeLog of gdb
> 
> --- gdb.orig/ChangeLog    2009-08-21 21:37:18.000000000 -0400
> +++ gdb.new/floating.ChangeLog    2009-08-21 21:37:13.000000000 -0400
> @@ -1,3 +1,9 @@
> +2009-08-21  Oza Pawandeep  <paawan1982@yahoo.com>
> +
> +        * i386-tdep.c:  Support for floating point recording.
> +        Records and Replay the i386 floating point registers,
> +        of i387 FPU.
> +
>  2009-08-19  Ralf Wildenhues  <Ralf.Wildenhues@gmx.de>
>  
>      * configure.ac: Call AC_DISABLE_OPTION_CHECKING.
> 
> 
> 2) there has been work done on arm-tdep.c as I see ChangeLog 
> (as I was also paralelly working, but I was not sure about already work going 
> on)
> The progress was slow because I changed organisation : (
> 
> I am not sure how much work has been done on arm and what is left..
> 
> kindly clarify my understanding on point 1 and possibly on point 2.

Hello Oza,

If your changelog entry was left out, I appologize.  It was probably
my fault -- I'll fix it when I get back from the gcc summit next week.

As for point #2, I'm sure some work has taken place in ther arm-tdep.c
module, but as far as I am aware, nothing related to reverse debugging
has been checked in there.  I do recall reading a message or two from
somebody else (not a regular contributer) who expressed an interest in
implementing reverse debugging for arm, but so far he has not submitted
any for review.

Good to hear from you, and sorry again if your changelog entry got left out.

Michael

Re: ChangeLog info missing ?

[Michael Snyder]

Michael Snyder wrote:
> paawan oza wrote:
>> Hi Michael,
>>
>> I have downloaded gdb 7.2 to continue working on reversible debugging. As I have 
>> observed the ChangeLog, there are 2 things.
>>
>> 1) below flaoting point changelog is missing from ChangeLog of gdb
>>
>> --- gdb.orig/ChangeLog    2009-08-21 21:37:18.000000000 -0400
>> +++ gdb.new/floating.ChangeLog    2009-08-21 21:37:13.000000000 -0400
>> @@ -1,3 +1,9 @@
>> +2009-08-21  Oza Pawandeep  <paawan1982@yahoo.com>
>> +
>> +        * i386-tdep.c:  Support for floating point recording.
>> +        Records and Replay the i386 floating point registers,
>> +        of i387 FPU.
>> +
>>  2009-08-19  Ralf Wildenhues  <Ralf.Wildenhues@gmx.de>
>>  
>>      * configure.ac: Call AC_DISABLE_OPTION_CHECKING.
>>
>>
>> 2) there has been work done on arm-tdep.c as I see ChangeLog 
>> (as I was also paralelly working, but I was not sure about already work going 
>> on)
>> The progress was slow because I changed organisation : (
>>
>> I am not sure how much work has been done on arm and what is left..
>>
>> kindly clarify my understanding on point 1 and possibly on point 2.
> 
> Hello Oza,
> 
> If your changelog entry was left out, I appologize.  It was probably
> my fault -- I'll fix it when I get back from the gcc summit next week.
> 
> As for point #2, I'm sure some work has taken place in ther arm-tdep.c
> module, but as far as I am aware, nothing related to reverse debugging
> has been checked in there.  I do recall reading a message or two from
> somebody else (not a regular contributer) who expressed an interest in
> implementing reverse debugging for arm, but so far he has not submitted
> any for review.
> 
> Good to hear from you, and sorry again if your changelog entry got left out.
> 
> Michael
> 

Hello Oza,

Your changelog entry did not get left out.  You can find it in
src/gdb/ChangeLog-2009.  You may not have realized that we start
a new ChangeLog file at the beginning of each year.

Cheers,
Michael

Re: ChangeLog info missing ?

[paawan oza]

Hi Michael,

1)
sorry for not noticing challog 2009. : (

but I am confused with outer Changelog because, if you see patch mentioned in 
below mail, which if checked in, will go to  '/Changelog' in the root directory 
itself, 

where 

I find the entry

2009-08-19  Ralf Wildenhues  <Ralf.Wildenhues@gmx.de>
        * configure.ac: Call AC_DISABLE_OPTION_CHECKING.

but, the patch entry missing, looks like the patch is not applied 
so in conclusion, appropriately correcting my understanding, each directory has 
changelog and changelog file is only applicable to be modified if developer has 
modified contents of that directory. 

Outer Changelog is never affected.
right ?

2) Ok, I think I need to go thorugh arm-tdep.c, as I saw there has been lots of 
changes done in 2010, but was not sure exactly for what, as there are some huge 
changes, If I have any questions after going through, I will try to post them.

Regards,
Oza.




----- Original Message ----
From: Michael Snyder <msnyder@vmware.com>
To: paawan oza <paawan1982@yahoo.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Sent: Sun, October 24, 2010 1:32:14 AM
Subject: Re: ChangeLog info missing ?

Michael Snyder wrote:
> paawan oza wrote:
>> Hi Michael,
>> 
>> I have downloaded gdb 7.2 to continue working on reversible debugging. As I 
>>have observed the ChangeLog, there are 2 things.
>> 
>> 1) below flaoting point changelog is missing from ChangeLog of gdb
>> 
>> --- gdb.orig/ChangeLog    2009-08-21 21:37:18.000000000 -0400
>> +++ gdb.new/floating.ChangeLog    2009-08-21 21:37:13.000000000 -0400
>> @@ -1,3 +1,9 @@
>> +2009-08-21  Oza Pawandeep  <paawan1982@yahoo.com>
>> +
>> +        * i386-tdep.c:  Support for floating point recording.
>> +        Records and Replay the i386 floating point registers,
>> +        of i387 FPU.
>> +
>>  2009-08-19  Ralf Wildenhues  <Ralf.Wildenhues@gmx.de>
>>       * configure.ac: Call AC_DISABLE_OPTION_CHECKING.
>> 
>> 
>> 2) there has been work done on arm-tdep.c as I see ChangeLog (as I was also 
>>paralelly working, but I was not sure about already work going on)
>> The progress was slow because I changed organisation : (
>> 
>> I am not sure how much work has been done on arm and what is left..
>> 
>> kindly clarify my understanding on point 1 and possibly on point 2.
> 
> Hello Oza,
> 
> If your changelog entry was left out, I appologize.  It was probably
> my fault -- I'll fix it when I get back from the gcc summit next week.
> 
> As for point #2, I'm sure some work has taken place in ther arm-tdep.c
> module, but as far as I am aware, nothing related to reverse debugging
> has been checked in there.  I do recall reading a message or two from
> somebody else (not a regular contributer) who expressed an interest in
> implementing reverse debugging for arm, but so far he has not submitted
> any for review.
> 
> Good to hear from you, and sorry again if your changelog entry got left out.
> 
> Michael
> 

Hello Oza,

Your changelog entry did not get left out.  You can find it in
src/gdb/ChangeLog-2009.  You may not have realized that we start
a new ChangeLog file at the beginning of each year.

Cheers,
Michael


      

Re: ChangeLog info missing ?

[Tom Tromey]

>>>>> ">" == paawan oza <paawan1982@yahoo.com> writes:

>> but I am confused with outer Changelog because, if you see patch
>> mentioned in below mail, which if checked in, will go to '/Changelog'
>> in the root directory itself,

If someone applies a patch manually he usually has to know which
ChangeLog to modify.  Ordinarily this isn't hard.

>> so in conclusion, appropriately correcting my understanding, each
>> directory has changelog and changelog file is only applicable to be
>> modified if developer has modified contents of that directory.

Yes.  If you modify a file, you must modify the nearest ChangeLog.  That
is, you start in the file's directory and go upwards until you find a
ChangeLog file.

>> Outer Changelog is never affected.
>> right ?

Yes.

Tom