This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
RE: breakpoints/2120: "info break" output not good when cond is a function call with string arg
- From: "Rohit Gulati" <rgulati at cadence dot com>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 28 Apr 2006 20:58:02 -0000
- Subject: RE: breakpoints/2120: "info break" output not good when cond is a function call with string arg
- Reply-to: "Rohit Gulati" <rgulati at cadence dot com>
The following reply was made to PR breakpoints/2120; it has been noted by GNATS.
From: "Rohit Gulati" <rgulati@cadence.com>
To: <gdb-gnats@sources.redhat.com>, <nobody@sources.redhat.com>
Cc:
Subject: RE: breakpoints/2120: "info break" output not good when cond is a function call with string arg
Date: Fri, 28 Apr 2006 13:53:59 -0700
Hi,
I debugged the problem reported in GDB bug breakpoints/2120 and have a
fix. I changed the file src/expprint.c, function print_subexp_standard,
switch case OP_ARRAY:
Please review the change and let me know if it is ok:
file 1 .../gdb/src/gdb-6.3/gdb/expprint.c
********************************
-----[242-243 changed to 242-245]-----
< && exp->elts[pc + 5].type =3D=3D builtin_type_char
< && exp->language_defn->la_language =3D=3D language_c
---
> /*&& exp->elts[pc + 5].type =3D=3D builtin_type_char*/
> && exp->elts[pc + 5].type =3D=3D builtin_type
(current_gdbarch)->builtin_char
> && (exp->language_defn->la_language =3D=3D language_c ||=20
> exp->language_defn->la_language =3D=3D language_cplus) )
-----[257 changed to 259-260]-----
< || exp->elts[pc + 1].type !=3D builtin_type_char)
---
> /*|| exp->elts[pc + 1].type !=3D builtin_type_char*/
> || exp->elts[pc + 1].type !=3D builtin_type
(current_gdbarch)->builtin_char)
>-----Original Message-----
>From: gdb-gnats@sources.redhat.com=20
>[mailto:gdb-gnats@sources.redhat.com]=20
>Sent: Wednesday, April 26, 2006 4:48 PM
>To: Rohit Gulati
>Subject: Re: breakpoints/2120: "info break" output not good=20
>when cond is a function call with string arg
>
>Thank you very much for your problem report.
>It has the internal identification `breakpoints/2120'.
>The individual assigned to look at your
>report is: unassigned.=20
>
>>Category: breakpoints
>>Responsible: unassigned
>>Synopsis: "info break" output not good when cond is a=20
>function call with string arg
>>Arrival-Date: Wed Apr 26 23:48:01 GMT 2006
>