Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Cristian Diaconu <cristian.diaconu@sap-ag.de>
To: "'Cygnus GDB-bugs'"
	<IMCEAMLP001UNIX-gdb-bugs+40cygnus+2Ecom@sap-ag.de>,
	"'Cygnus - GDB'" <gdb@cygnus.com>
Subject: Unknown type reported on Solaris x86 for char[xxx]
Date: Thu, 22 Apr 1999 14:09:00 -0000	[thread overview]
Message-ID: <2BC52EF1968FD211B3AB00805FE6FE82754518@uspalx21.pal.sap-ag.de> (raw)

This could be a problem with egcs/gcc,  but it manifests itself in gdb,
therefore I present it here in hope of someone cross-referencing it if
needed.

I work on Solaris x86 with egcs 1.1.2 and gdb 4.17. (The same behavior is
evident with gdb 4.18.) I also have a Linux workstation. The following code
produces different results:

Class A
{
public:
   char m_char[25];
};

int main()
{
   A a;
   return 0;
}

I load this program in gdb and break on main. When I issue "ptype b" command
in gdb, on Solaris I get the following output:

*	ptype a
struct A {
   <unknown type>
};

On Linux however, the output is:
Class A {
   Char m_char[25];
};

Any help is greatly appreciated.

Thank you

Cristian Diaconu


WARNING: multiple messages have this Message-ID
From: Cristian Diaconu <cristian.diaconu@sap-ag.de>
To: "'Cygnus GDB-bugs'"
	<IMCEAMLP001UNIX-gdb-bugs+40cygnus+2Ecom@sap-ag.de>,
	"'Cygnus - GDB'" <gdb@cygnus.com>
Subject: Unknown type reported on Solaris x86 for char[xxx]
Date: Thu, 22 Apr 1999 14:55:00 -0000	[thread overview]
Message-ID: <2BC52EF1968FD211B3AB00805FE6FE82754518@uspalx21.pal.sap-ag.de> (raw)
Message-ID: <19990422145500.zLUNyVM1um271myM-6TkZ4HozW8vEa4wWj05d5kiKMM@z> (raw)

This could be a problem with egcs/gcc,  but it manifests itself in gdb,
therefore I present it here in hope of someone cross-referencing it if
needed.

I work on Solaris x86 with egcs 1.1.2 and gdb 4.17. (The same behavior is
evident with gdb 4.18.) I also have a Linux workstation. The following code
produces different results:

Class A
{
public:
   char m_char[25];
};

int main()
{
   A a;
   return 0;
}

I load this program in gdb and break on main. When I issue "ptype b" command
in gdb, on Solaris I get the following output:

*	ptype a
struct A {
   <unknown type>
};

On Linux however, the output is:
Class A {
   Char m_char[25];
};

Any help is greatly appreciated.

Thank you

Cristian Diaconu
From cristian.diaconu@sap-ag.de Thu Apr 22 14:57:00 1999
From: Cristian Diaconu <cristian.diaconu@sap-ag.de>
To: "'Cygnus - GDB'" <gdb@cygnus.com>, "'Cygnus GDB-bugs'" <IMCEAMLP001UNIX-gdb-bugs+40cygnus+2Ecom@sap-ag.de>
Subject: Problem accessing inheritance information on Solaris - works fine in Linux
Date: Thu, 22 Apr 1999 14:57:00 -0000
Message-id: <2BC52EF1968FD211B3AB00805FE6FE82754514@uspalx21.pal.sap-ag.de>
X-SW-Source: 1999-04/msg00059.html
Content-length: 900

This could be a problem with egcs/gcc,  but it manifests itself in gdb,
therefore I present it here in hope of someone cross-referencing it if
needed.

I work on Solaris with egcs 1.1.2 and gdb 4.17. (The same behavior is
evident with gdb 4.18.) I also have a Linux workstation. The following code
produces different results:

Class A
{
public:
   int m_intA;
};

class B : public A
{
public:
   int m_intB;
};

int main()
{
   B b;
   return 0;
}

I load this program in gdb and break on main. When I issue "ptype b" command
in gdb, on Solaris I get the following output:

*	ptype b
struct B {
   int m_intB;
};

On Linux however, the output is:
Class B : public A {
   Int m_intB;
};

Obviously on Solaris the debugger cannot access the inheritance information.
Also, the debugger does not realize that B is a class and not a struct.

Any help is greatly appreciated.

Thank you

Cristian Diaconu


             reply	other threads:[~1999-04-22 14:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-04-22 14:09 Cristian Diaconu [this message]
1999-04-22 14:55 ` Cristian Diaconu

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=2BC52EF1968FD211B3AB00805FE6FE82754518@uspalx21.pal.sap-ag.de \
    --to=cristian.diaconu@sap-ag.de \
    --cc=IMCEAMLP001UNIX-gdb-bugs+40cygnus+2Ecom@sap-ag.de \
    --cc=gdb@cygnus.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