Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Fred Fish <fnf@specifix.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Jim Blandy <jimb@red-bean.com>,
	gdb-patches@sourceware.org, 	fnf@specifix.com
Subject: Re: [PATCH] Fix ptype problem printing typedefs defined differently in different compilation units
Date: Mon, 23 Jan 2006 16:43:00 -0000	[thread overview]
Message-ID: <200601231143.22560.fnf@specifix.com> (raw)
In-Reply-To: <20060123161210.GC17767@nevyn.them.org>

On Monday 23 January 2006 11:12, Daniel Jacobowitz wrote:
> I don't understand.  What doesn't work?  Is it something that works
> without the patch, or not?

Doesn't work without the patch, as it uses the type for the first
symtab it happens to find that has a definition for that type.

> I don't understand how your examples relate
> to your description of the problem anymore.

OK, I've attached a typescript at the bottom of this mail showing how
it fails in the presence of a core and/or running executable.

> > So something like the following, which currently produces an error:
> > 
> >   (gdb) ptype 'main.c'::foo
> >   Cannot look up value of a typedef
> 
> Well that seems like a reasonable thing to fix anyway; ptype (and
> sizeof!) should be using a non-side-effects evaluation anyway.

I can look at this, though it may be a week or so.

-Fred

============================================================================

Here is a simple testcase

$ cat main.c
typedef long foo;
foo longfoo;

main ()
{
  extern charfoo (char);
  extern intfoo (int);
  int a = 5;

  a = intfoo (a);
  a = charfoo (a);
  printf ("a = %d (should be 20)\n", a);
  *(char *)0 = 0;
}

$ cat int.c
typedef int foo;

intfoo (foo a)
{
  return (2 * a);
}

$ cat char.c
typedef char foo;

charfoo (foo a)
{
  return (2 * a);
}

============================================================================

Build testcase on Fedora Core 4 and generate corefile

$ make
gcc -g  --save-temps   -c -o main.o main.c
main.c: In function ‘main’:
main.c:12: warning: incompatible implicit declaration of built-in function ‘printf’
gcc -g  --save-temps   -c -o char.o char.c
gcc -g  --save-temps   -c -o int.o int.c
gcc -o main main.o char.o int.o 

$ ./main
a = 20 (should be 20)
Segmentation fault (core dumped)
$ mv core.* core

============================================================================

Use gdb to examine just the executable file

$ ../gdb main
(gdb) list main
1	typedef long foo;
2	foo longfoo;
3	
4	main ()
5	{
6	  extern charfoo (char);
7	  extern intfoo (int);
8	  int a = 5;
9	
10	  a = intfoo (a);
(gdb) ptype foo
type = long int			<===== OK
(gdb) list charfoo
1	typedef char foo;
2	
3	charfoo (foo a)
4	{
5	  return (2 * a);
6	}
(gdb) ptype foo
type = char			<===== OK
(gdb) list intfoo
1	typedef int foo;
2	
3	intfoo (foo a)
4	{
5	  return (2 * a);
6	}
(gdb) ptype foo
type = int			<===== OK
(gdb) quit

============================================================================

Use gdb to examine the executable file and core file

$ ../gdb main core
#0  0x080483de in main () at main.c:13
13	  *(char *)0 = 0;
(gdb) list main
1	typedef long foo;
2	foo longfoo;
3	
4	main ()
5	{
6	  extern charfoo (char);
7	  extern intfoo (int);
8	  int a = 5;
9	
10	  a = intfoo (a);
(gdb) ptype foo
type = long int			<===== OK
(gdb) list charfoo
1	typedef char foo;
2	
3	charfoo (foo a)
4	{
5	  return (2 * a);
6	}
(gdb) ptype foo
type = long int			<===== Prints using frame context
(gdb) list intfoo
1	typedef int foo;
2	
3	intfoo (foo a)
4	{
5	  return (2 * a);
6	}
(gdb) ptype foo
type = long int			<===== Prints using frame context
(gdb) quit

============================================================================




  reply	other threads:[~2006-01-23 16:43 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-03 20:17 Fred Fish
2006-01-03 23:15 ` Jim Blandy
2006-01-04  2:46   ` Fred Fish
2006-01-04  3:45     ` Jim Blandy
2006-01-04 11:15       ` Fred Fish
2006-01-04 21:04       ` Fred Fish
2006-01-05  0:21         ` Jim Blandy
2006-01-05  0:26         ` Jim Blandy
2006-01-05  0:54           ` Daniel Jacobowitz
2006-01-05  4:47             ` Jim Blandy
2006-01-15 18:48         ` Daniel Jacobowitz
2006-01-16  4:22           ` Jim Blandy
2006-01-23 15:27             ` Fred Fish
2006-01-23 16:12               ` Daniel Jacobowitz
2006-01-23 16:43                 ` Fred Fish [this message]
2006-01-23 19:17                   ` Jim Blandy
2006-01-23 19:35                     ` Fred Fish
2006-01-23 20:45                       ` Jim Blandy
2006-02-11  0:39                         ` Fred Fish
2006-02-11  0:39                         ` Fred Fish
2006-02-11 18:35                           ` Daniel Jacobowitz
2006-02-11 19:08                             ` Eli Zaretskii
2006-02-11 20:13                               ` Daniel Jacobowitz
2006-02-11 20:01                             ` Fred Fish
2006-02-11 20:21                               ` Daniel Jacobowitz
2006-02-12 18:49                                 ` Fred Fish
2006-02-14 14:11                                   ` Daniel Jacobowitz
2006-02-14 18:47                                     ` Fred Fish
2006-02-17  0:17                                     ` Fred Fish
2006-02-17  9:15                                       ` Eli Zaretskii
2006-02-17 13:36                                         ` Fred Fish
2006-02-17 20:32                                         ` Fred Fish
2006-02-18  9:27                                           ` Eli Zaretskii
2006-02-18 22:19                                       ` Daniel Jacobowitz
2006-02-20 15:47                                       ` Fred Fish
2006-02-20 16:23                                         ` Daniel Jacobowitz
2006-05-17 19:04                                           ` Fred Fish
2006-01-24 15:23                     ` [commit] " Fred Fish

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200601231143.22560.fnf@specifix.com \
    --to=fnf@specifix.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jimb@red-bean.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox