Pierre Muller | 1 Apr 2011 07:12
Picon

RE: [RFC 1/9] Unify windows specifics into common/windows-hdep files

> > From: "Pierre Muller" <pierre.muller <at> ics-cnrs.unistra.fr>
> > Cc: <gdb-patches <at> sourceware.org>
> > Date: Wed, 30 Mar 2011 23:32:36 +0200
> >
> > > > +#undef _G_SUFFIX
> > >
> > > I think the C Standard says that macros whose name begins with an
> > > underscore and a capital letter are reserved.  Applications should not
> > > use such macros.
> >
> >   But we are also using __USEWIDE before my patch ...
> >  or do you mean that two underscores are OK?
> 
> No, AFAIK macros that begin with two underscores are also reserved.

  But nobody protested for __USEWIDE nor for __PMAX for instance...
But checking gdb directory, it seems that are only a fee macros 
starting with an underscore.

> >   I completely remove __USEWIDE and tried to replace it by this new
> > USE_WIDE_WINAPI.
> >   Or is this __USEWIDE macro used anywhere else than inside GDB code?
> 
> I don't think so, but maybe someone else could tell for sure.
> 
> >   Should I rather call the macro USE_UNICODE_WINAPI
> >  (and USE_ANSI_WINAPI to force ANSI version?)
> 
> I don't think it matters what the macro is called.

(Continue reading)

Jan Kratochvil | 1 Apr 2011 07:25
Picon
Favicon

Regression: Re: FYI: fix varobj bug with python iterator errors

Hi Tom,

On Thu, 31 Mar 2011 21:58:45 +0200, Tom Tromey wrote:
> I'm checking this in.
[...]
> Built and regtested on x86-64 (compile farm).
[...]
> 2011-03-31  Tom Tromey  <tromey <at> redhat.com>
> 
> 	* varobj.c (update_dynamic_varobj_children): Properly handle
> 	errors from iterator.
> 
> 2011-03-31  Tom Tromey  <tromey <at> redhat.com>
> 
> 	* gdb.python/py-prettyprint.py (exception_flag): New global.
> 	(NoStringContainerPrinter._iterator.next): Check it.
> 	* gdb.python/py-prettyprint.c (main): New variable nstype2.
> 	* gdb.python/py-mi.exp: Set exception_flag and do more tests.

This commit 837e99b31775e6a75a593259738924bf050650d2 has regressions on
{x86_64-m32,i686}-{fedora15,rawhide}-linux-gnu, it still PASSes on
x86_64-{fedora15,rawhide}-linux-gnu, it also still PASSes on
{x86_64,x86_64-m32,i686}-fedora{13,14}-linux-gnu.

Thanks,
Jan

diff -dup -rU9999 pass/gdb.sum fail/gdb.sum
--- pass/gdb.sum	2011-04-01 07:18:38.000000000 +0200
+++ fail/gdb.sum	2011-04-01 07:20:28.000000000 +0200
(Continue reading)

Eli Zaretskii | 1 Apr 2011 10:39
Picon

Re: [RFC 1/9] Unify windows specifics into common/windows-hdep files

> From: "Pierre Muller" <pierre.muller <at> ics-cnrs.unistra.fr>
> Cc: <gdb-patches <at> sourceware.org>
> Date: Fri, 1 Apr 2011 07:12:42 +0200
> 
> > > From: "Pierre Muller" <pierre.muller <at> ics-cnrs.unistra.fr>
> > > Cc: <gdb-patches <at> sourceware.org>
> > > Date: Wed, 30 Mar 2011 23:32:36 +0200
> > >
> > > > > +#undef _G_SUFFIX
> > > >
> > > > I think the C Standard says that macros whose name begins with an
> > > > underscore and a capital letter are reserved.  Applications should not
> > > > use such macros.
> > >
> > >   But we are also using __USEWIDE before my patch ...
> > >  or do you mean that two underscores are OK?
> > 
> > No, AFAIK macros that begin with two underscores are also reserved.
> 
>   But nobody protested for __USEWIDE nor for __PMAX for instance...
> But checking gdb directory, it seems that are only a fee macros 
> starting with an underscore.

Again, I think it's bad practice to use such macros, but that's me.
If no one else cares, you can disregard me on that account.

> > > > > +# define CreateProcess CreateProcessW
> > > > > +# define GetSystemDirectory GetSystemDirectoryW
> > > > > +# define windows_strlen wcslen
> > > >
(Continue reading)

Pierre Muller | 1 Apr 2011 11:23
Picon

RE: [RFC 1/9] Unify windows specifics into common/windows-hdep files


> -----Message d'origine-----
> De : gdb-patches-owner <at> sourceware.org [mailto:gdb-patches-
> owner <at> sourceware.org] De la part de Eli Zaretskii
> Envoyé : vendredi 1 avril 2011 10:39
> À : Pierre Muller
> Cc : gdb-patches <at> sourceware.org
> Objet : Re: [RFC 1/9] Unify windows specifics into common/windows-hdep
files
> 
> > From: "Pierre Muller" <pierre.muller <at> ics-cnrs.unistra.fr>
> > Cc: <gdb-patches <at> sourceware.org>
> > Date: Fri, 1 Apr 2011 07:12:42 +0200
> >
> > > > From: "Pierre Muller" <pierre.muller <at> ics-cnrs.unistra.fr>
> > > > Cc: <gdb-patches <at> sourceware.org>
> > > > Date: Wed, 30 Mar 2011 23:32:36 +0200
> > > >
> > > > > > +#undef _G_SUFFIX
> > > > >
> > > > > I think the C Standard says that macros whose name begins with an
> > > > > underscore and a capital letter are reserved.  Applications should
> not
> > > > > use such macros.
> > > >
> > > >   But we are also using __USEWIDE before my patch ...
> > > >  or do you mean that two underscores are OK?
> > >
> > > No, AFAIK macros that begin with two underscores are also reserved.
> >
(Continue reading)

Ulrich Weigand | 1 Apr 2011 13:58
Picon
Favicon

Re: [rfc, arm] Always use correct execution state for single-step breakpoints

> gdb/
> 	* arm-tdep.h (arm_insert_single_step_breakpoint): Add prototype.
> 	* arm-tdep.c (arm_override_mode): New global.
> 	(arm_pc_is_thumb): Respect arm_override_mode.  Remove single-step
> 	execution mode heuristics.
> 	(thumb_get_next_pc_raw): Remove INSERT_BKTP argument; always insert
> 	second single-step breakpoint if needed, using
> 	arm_insert_single_step_breakpoint.
> 	(arm_get_next_pc_raw): Remove INSERT_BKTP argument.  Only handle
> 	ARM execution mode, do not call thumb_get_next_pc_raw.
> 	(arm_get_next_pc): Encode execution mode in return value.  Call
> 	either arm_get_next_pc_raw or thumb_get_next_pc_raw.
> 	(arm_insert_single_step_breakpoint): New function.
> 	(arm_software_single_step): Call it.
> 	* arm-linux-tdep.c (arm_linux_sigreturn_return_addr): Add IS_THUMB
> 	argument to return execution mode of sigreturn target.
> 	(arm_linux_syscall_next_pc): Use it.
> 	(arm_linux_copy_svc): Update call.
> 	(arm_linux_software_single_step): Call
> 	arm_insert_single_step_breakpoint.
> 
> gdb/testsuite/
> 	* gdb.arch/thumb-singlestep.S: New file.
> 	* gdb.arch/thumb-singlestep.exp: Likewise.

I've checked this in now.

Bye,
Ulrich

(Continue reading)

Pedro Alves | 1 Apr 2011 17:09

FAIL: gdb.cp/cpexprs.exp: list base::overload(void)

I've been seeing these failures for a long while:

FAIL: gdb.cp/cpexprs.exp: list base::overload(void)
FAIL: gdb.cp/cpexprs.exp: setting breakpoint at base::overload(void)
FAIL: gdb.cp/cpexprs.exp: continue to base::overload(void)

gdb.log shows:

 list base::overload(void)
 the class `base' does not have any method instance named overload(void)
 (gdb) FAIL: gdb.cp/cpexprs.exp: list base::overload(void)

and indeed, base::overload(void) is const:

  // Some overloaded methods
  int overload (void) const { return 0; } // base::overload(void) const
  int overload (int i) const { return 1; } // base::overload(int) const
  int overload (short s) const { return 2; } // base::overload(short) const
  int overload (long l) const { return 3; } // base::overload(long) const
  int overload (char* a) const { return 4; } // base::overload(char*) const
  int overload (base& b) const { return 5; } // base::overload(base&) const

cpexprs.exp test all the other overloads with an explicit "const", but
the (void) one is tested for both const and non-nonst variants:

> # Overloaded methods (all are const -- we try to use the void
> # method with and without specifying "const")

Why is the non-const variant tried and expected to pass?

(Continue reading)

Tom Tromey | 1 Apr 2011 17:21
Picon
Favicon

Re: [patch] Fix gdb.cp/ovsrch.exp C++ regression-by-.gdb_index

>>>>> "Jan" == Jan Kratochvil <jan.kratochvil <at> redhat.com> writes:

Jan> 2011-03-30  Jan Kratochvil  <jan.kratochvil <at> redhat.com>
Jan> 	* dwarf2read.c (find_slot_in_mapped_hash): New variable back_to,
Jan> 	initialize it.  Delay HASH initialization.  Strip the part after open
Jan> 	parenthesis for languages with qualifiers.  Call do_cleanups.

Looks ok to me.

thanks,
Tom

Pedro Alves | 1 Apr 2011 17:23

Fix build (was: Re: [rfc, arm] Always use correct execution state for single-step breakpoints)

On Friday 01 April 2011 12:58:44, Ulrich Weigand wrote:
> > gdb/
> >       * arm-tdep.h (arm_insert_single_step_breakpoint): Add prototype.

This broke arm-bsd or --enable-targets=all builds:

In file included from ../../src/gdb/armnbsd-tdep.c:26:
../../src/gdb/arm-tdep.h:315: error: ‘struct address_space’ declared inside parameter list
../../src/gdb/arm-tdep.h:315: error: its scope is only this definition or declaration, which is
probably not what you want

I've applied the obvious fix below.

--

-- 
Pedro Alves

2011-04-01  Pedro Alves  <pedro <at> codesourcery.com>

	gdb/
	* arm-tdep.h (struct address_space): Add forward declaration.

---
 gdb/arm-tdep.h |    1 +
 1 file changed, 1 insertion(+)

Index: src/gdb/arm-tdep.h
===================================================================
--- src.orig/gdb/arm-tdep.h	2011-04-01 15:08:25.000000000 +0100
+++ src/gdb/arm-tdep.h	2011-04-01 15:29:30.899770002 +0100
 <at>  <at>  -23,6 +23,7  <at>  <at> 
(Continue reading)

Ulrich Weigand | 1 Apr 2011 17:41
Picon
Favicon

Re: Fix build (was: Re: [rfc, arm] Always use correct execution state for single-step breakpoints)

Pedro Alves wrote:
> On Friday 01 April 2011 12:58:44, Ulrich Weigand wrote:
> > > gdb/
> > >       * arm-tdep.h (arm_insert_single_step_breakpoint): Add prototype.
> 
> This broke arm-bsd or --enable-targets=3Dall builds:

Oops, sorry for that.

> I've applied the obvious fix below.

Thanks!

Bye,
Ulrich

--

-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand <at> de.ibm.com

Thiago Jung Bauermann | 1 Apr 2011 17:44
Picon

Re: [RFC] Cleanup breakpoint_re_set_one

Hi,

On Mon, 2011-03-21 at 18:14 -0300, Thiago Jung Bauermann wrote:
> Tested with no regressions on ppc-linux and ppc64-linux. WDYT?

This is a refreshed version of the patch, which applies on
today's CVS HEAD.
-- 
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center

2011-04-01  Thiago Jung Bauermann  <bauerman <at> br.ibm.com>

	* breakpoint.c (addr_string_to_sals): Cleanup logic of the
	conditon expressions in the error handling code.

diff --git a/gdb/breakpoint.c b/gdb/breakpoint.c
index 3b1367b..6d7c234 100644
--- a/gdb/breakpoint.c
+++ b/gdb/breakpoint.c
 <at>  <at>  -10979,33 +10979,26  <at>  <at>  addr_string_to_sals (struct breakpoint *b, char *addr_string, int *found)
 	sals = decode_line_1 (&s, 1, (struct symtab *) NULL, 0,
 			      NULL, &not_found);
     }
-  if (e.reason < 0)
-    {
-      int not_found_and_ok = 0;
-      /* For pending breakpoints, it's expected that parsing will
-	 fail until the right shared library is loaded.  User has
(Continue reading)


Gmane