Hui Zhu | 1 Nov 10:02 2010
Picon

Re: GDB 7.2.1 release?

And:
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/tracepoint.c.diff?cvsroot=src&r1=1.196&r2=1.197

Thanks,
Hui

On Thu, Oct 28, 2010 at 11:44, Hui Zhu <teawater <at> gmail.com> wrote:
> Suggest these 2 bug fixes for tracepoint:
>
> http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/tracepoint.c.diff?cvsroot=src&r1=1.194&r2=1.195
> http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/tracepoint.c.diff?cvsroot=src&r1=1.195&r2=1.196
>
> Thanks,
> Hui
>
> On Thu, Oct 28, 2010 at 10:49, Joel Brobecker <brobecker <at> adacore.com> wrote:
>> Hello everyone,
>>
>> It's time to ask ourselves whether we want to make a minor release off
>> of the 7.2 branch. According to the tentative schedule, we were planning
>> on making it around 3 months after the 7.2 release, which would be Dec 2nd.
>>
>> First, I would like to determine which changes we've made that should go
>> in the branch. So far, we have 3 changes, but there are probably more
>> changes that could go in the branch...
>>
>> Please let us know if you are aware of any such change.
>>
>> Thanks!
>> --
(Continue reading)

Pedro Alves | 1 Nov 10:23 2010

Re: GDB 7.2.1 release?

On Monday 01 November 2010 09:02:18, Hui Zhu wrote:
> On Thu, Oct 28, 2010 at 11:44, Hui Zhu <teawater <at> gmail.com> wrote:
> > Suggest these 2 bug fixes for tracepoint:
> >
> > http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/tracepoint.c.diff?cvsroot=src&r1=1.194&r2=1.195
> > http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/tracepoint.c.diff?cvsroot=src&r1=1.195&r2=1.196

> And:
> http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/tracepoint.c.diff?cvsroot=src&r1=1.196&r2=1.197

It's fine with me to put these on the 7.2 branch

--

-- 
Pedro Alves

Liu, Lei | 1 Nov 10:35 2010

Looking up enum constant symbols from C++ base classes

Hi,

I have a problem when debugging a C++ program.  Here is my test case.

#include <cstdio>

class A {
public:
   enum E {X,Y,Z};
};

class B : A {
public:
   void test(E e);
};

void B::test(E e) {
   if (e == X) {        //b 14 if e==X
     printf("%d\n",e);
   }
}

int main() {
   B b;
   b.test(A::X);
   return 0;
}

Compiled by gcc-4.1.2 with -O0 -g.

(Continue reading)

paawan oza | 1 Nov 11:34 2010
Picon

Re: with target sim gdb hangs....summary

any inputs to resolve target sim problem ?
please refer to the mail below.
as it has stooped my progress on arm reversible : (

----- Original Message ----
From: paawan oza <paawan1982 <at> yahoo.com>
To: gdb <at> sourceware.org
Sent: Sat, October 30, 2010 9:56:12 AM
Subject: with target sim gdb hangs....summary

Hi

I have posted several mails regarding arm binaries running under gdb target sim 
command.
here is the brief summary, please give inputs to resolve it if possible.

1) 
gdb compiled with
--host=i686-pc-linux-gnu --target=arm-elf

tool chain used 
arm-none-linux-gnueabi

gdb hangs under

target sim
file test.out.
load
run (on this command it tries to run arm executable but it hangs)

(Continue reading)

Joel Brobecker | 1 Nov 15:14 2010

Re: GDB 7.2.1 release?

> > > http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/tracepoint.c.diff?cvsroot=src&r1=1.194&r2=1.195
> > > http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/tracepoint.c.diff?cvsroot=src&r1=1.195&r2=1.196
> 
> > And:
> > http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/tracepoint.c.diff?cvsroot=src&r1=1.196&r2=1.197
> 
> It's fine with me to put these on the 7.2 branch

Then, please go ahead and commit them in the branch.

--

-- 
Joel

Nick Clifton | 1 Nov 18:13 2010
Picon

Re: RFC: Add zlib source to src CVS resposity

Hi Guys,

 >>> So this becomes a question for the binutils maintainers: do
>>> the binutils want to be self-contained, or do they want to follow the
>>> path of gcc and require additional libraries to be installed before a
>>> build can succeed?

As I see it the pros of having a copy of the zlib sources in the 
binutils tree are that:

   * The tools can be built on a host that does not have
     zlib installed.

   * We can be sure exactly which version of zlib is being
     used.

   * It simplifies our configure scripts and sources.  We
     always know that zlib is present and the API to use.

Whereas the cons of having our own copy of zlib are that:

   * We have to manually import any bug-fixes or enhancements
     to the official zlib sources.  Which means that we have
     to watch the zlib sources and be ready to evaluate any
     changes.

   * We have to make sure that zlib will build on all of the
     hosts that we care about.  Should the situation arise
     where the zlib does not build on a particular host, and
     the zlib maintainers are not interested in making it
(Continue reading)

Daniel Jacobowitz | 1 Nov 18:19 2010

Re: RFC: Add zlib source to src CVS resposity

On Mon, Nov 01, 2010 at 05:13:44PM +0000, Nick Clifton wrote:
> At the moment I feel that the pros outweigh the cons.  What do other
> people think ?

I was asked not to include expat in GDB, which was a similar
situation.  I don't remember if this was an FSF issue; I know that the
FSF, in general, dislikes duplicated source code in packages, but I
don't know if they care when the duplicated bits are non-GNU.  There
were definitely GDB developers that disliked bundling expat, so
perhaps you can find the reasons in the archives.

--

-- 
Daniel Jacobowitz
CodeSourcery

Tom Tromey | 1 Nov 20:00 2010
Picon

Re: ChangeLog info missing ?

>>>>> ">" == paawan oza <paawan1982 <at> 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

Tom Tromey | 1 Nov 20:12 2010
Picon

Re: Looking up enum constant symbols from C++ base classes

>>>>> ">" == Liu, Lei <lei.liu2 <at> windriver.com> writes:

>> class A {
>> public:
>>   enum E {X,Y,Z};
>> };

>> I tried to plant a conditional breakpoint in line 14 as shown in comment
>> but got a error shows 'No symbol "X" in current context'.  The symbol
>> 'X' is accessible in that scope.  It seems that gdb has a problem to look
>> up enum constant symbols derived from base classes.

Yeah.

>> I added some code in cp_lookup_symbol_nonlocal to make gdb look up symbols
>> from all base classes.  It works fine.  Is this a right fix?

It might be, but we'd have to see the patch to be sure.

Tom

Alan Modra | 2 Nov 00:55 2010
Picon

Re: RFC: Add zlib source to src CVS resposity

On Mon, Nov 01, 2010 at 05:13:44PM +0000, Nick Clifton wrote:
>   * We have to make sure that zlib will build on all of the
>     hosts that we care about.  Should the situation arise
>     where the zlib does not build on a particular host, and
>     the zlib maintainers are not interested in making it
>     build there, then it will be down to us to fix it.  Or
>     else abandon compression support on that host.

This would mean we need to keep machinery to conditionally compile
in compressed debug support, removal of said support being HJ's stated
reason for importing zlib.

I'm against importing zlib into binutils, and I think we should keep
support of compressed debug sections conditional, to avoid potential
bootstrap problems or circular dependencies.

--

-- 
Alan Modra
Australia Development Lab, IBM


Gmane