Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Hillel (Sabba) Markowitz" <Sabba.Hillel@verizon.net>
To: Joel Brobecker <brobecker@gnat.com>
Cc: GDB help mailing list <gdb@sources.redhat.com>
Subject: Re: GDB build fails on DEC OSF V5.1a but not OSF V4.0f
Date: Fri, 20 Dec 2002 03:07:00 -0000	[thread overview]
Message-ID: <3E02F9F3.65E2EF1F@verizon.net> (raw)
In-Reply-To: <20021220101329.GF1137@gnat.com>



Joel Brobecker wrote:
> 
> > When built on DEC OSF V5.1A, gdb gets a seg fault.  When built on DEC
> > OSF 4.0f it runs correctly.  When copied from the DEC OSF V4.0f to the
> > DEC OSF V5.1A platform, gdb runs successfully.
> 
> It would be more helpful if you could send more details about your
> problem. For instance, which version of GDB did you build? Using which
> compiler? A simple program that we could use to reproduce your problem
> is also helpful. I just rebuilt 5.3 on Tru64 5.1A using GCC, and got the
> usual results from the testsuite.
> 
> --
> Joel

gcc-3.2.1 with a basic hellow world (though any test program works the
same

int main(int argc, char **argv)
{
  printf("hellow world\n");
 /* A a number of prints here  */
#ifdef __dec
  printf("__dec is defined\n");
#else
  printf("__dec is NOT defined\n");
#endif
/* Put in a bunch of variable defined tests as above */

.
.
.

}

That is all

compile with 

gcc -g testit.c -o testit

gdb testit


I did not run the test suite (gmake check) on the gdb installation.


-- 
Said the fox to the fish, "Join me ashore".
The fish are the Jews, Torah is our water.

Hillel (Sabba) Markowitz
sabbahem@bcpl.net, Sabba.Hillel@verizon.net


  reply	other threads:[~2002-12-20 11:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-19  9:18 Hillel (Sabba) Markowitz
2002-12-20  2:13 ` Joel Brobecker
2002-12-20  3:07   ` Hillel (Sabba) Markowitz [this message]
2002-12-20  3:18     ` Joel Brobecker
2002-12-20  3:37       ` Hillel (Sabba) Markowitz

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=3E02F9F3.65E2EF1F@verizon.net \
    --to=sabba.hillel@verizon.net \
    --cc=brobecker@gnat.com \
    --cc=gdb@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