Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Elizabeth Chastain <mec@shout.net>
To: drow@mvista.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Fix gdb/277 by separating types
Date: Sun, 12 May 2002 20:10:00 -0000	[thread overview]
Message-ID: <200205130310.g4D3A4R20206@duracef.shout.net> (raw)

I do build an object directory from scratch (just to avoid these
kinds of problems).

BTW I am using gcc 2.95.3, I don't know where you got 2.95.2 from.

I bet the difference in our machines is somewhere in libc.
I am using stock red hat linux 7.2 glibc, glibc 2.2.4-13.

It's reproducing on my machine.  Here's a shorter recipe:

  ./gdb gdb.base/break
  (gdb) break main
  (gdb) run
  (gdb) maint print symbols symbols_output

Have a look at the end of symbols_output in the tarball.
Mine is reproducibly crapping out in file 'init.c' here:

   typedef void (*__gconv_end_fct)();
   typedef int (*__gconv_fct)();
   struct __gconv_info {
       size_t __nsteps;
       struct __gconv_step *__steps;
       struct __gconv_step_data __data[0];
   };

   typedef int (*__gconv_init_fct)();
   struct __gconv_step {

When I do maint-print-symbols with gdb 5.2, it runs fine,
and gives me this output for __gconv_step:

   typedef int (*__gconv_init_fct)(struct __gconv_step *);
   struct __gconv_step {
       struct __gconv_loaded_object *__shlib_handle;
       const char *__modname;
       int __counter;
       char *__from_name;
       char *__to_name;
       int (*__fct)(struct __gconv_step *, struct __gconv_step_data *, const unsigned char **, const unsigned char *, unsigned char **, size_t *, int, int);
       int (*__init_fct)(struct __gconv_step *);
       void (*__end_fct)(struct __gconv_step *);
       int __min_needed_from;
       int __max_needed_from;
       int __min_needed_to;
       int __max_needed_to;
       int __stateful;
       void *__data;
   };

In the stack trace, I'm seeing it crap out on c_print_type of
__shlib_handle.  __gconv_loaded_object is a forward reference,
but it is not defined in this symtab: it is defined in a different
symtab.

Michael C


             reply	other threads:[~2002-05-13  3:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-12 20:10 Michael Elizabeth Chastain [this message]
2002-05-12 20:16 ` Daniel Jacobowitz
  -- strict thread matches above, loose matches on Subject: below --
2002-05-12 20:13 Michael Elizabeth Chastain
2002-05-12 19:19 Michael Elizabeth Chastain
2002-05-12 19:38 ` Daniel Jacobowitz
2002-05-12 17:53 Daniel Jacobowitz
2002-05-12 22:22 ` Eli Zaretskii
2002-05-13  6:30   ` Andrew Cagney
2002-05-13  6:41   ` Daniel Jacobowitz

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=200205130310.g4D3A4R20206@duracef.shout.net \
    --to=mec@shout.net \
    --cc=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.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