public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: "Matthew H Bemis" <bemis@iol.unh.edu>
To: "Elena Zannoni" <ezannoni@redhat.com>,
	"Mike Cleary" <mcleary@iol.unh.edu>
Cc: <gdb@sources.redhat.com>, "clp" <clp@iol.unh.edu>
Subject: RE: GDB *** [event-top.o] Error 1!!
Date: Thu, 20 Jun 2002 19:16:00 -0000	[thread overview]
Message-ID: <DJEHKIJNENDCOJNKEBGKCEJFDFAA.bemis@iol.unh.edu> (raw)
In-Reply-To: <15634.19855.893660.159800@localhost.redhat.com>

Elana,
Mike is building on an alphaev56, and he is building with the
bootstrap-gcc_3.0.4 baseline.
we'll try the patch tomorrow.
we'll let you know how it goes.
thanks!
Matt Bemis

-----Original Message-----
From: gdb-owner@sources.redhat.com
[mailto:gdb-owner@sources.redhat.com]On Behalf Of Elena Zannoni
Sent: Thursday, June 20, 2002 5:48 PM
To: Mike Cleary
Cc: gdb@sources.redhat.com; clp
Subject: Re: GDB *** [event-top.o] Error 1!!




There is a missing ifdef in there, I guess you must be one of the few
(the only one) triggering this.

Could you try this patch?

Index: event-top.c
===================================================================
RCS file: /cvs/uberbaum/gdb/event-top.c,v
retrieving revision 1.20
diff -u -p -r1.20 event-top.c
--- event-top.c	27 Mar 2002 21:20:15 -0000	1.20
+++ event-top.c	20 Jun 2002 21:46:36 -0000
@@ -514,8 +514,10 @@ command_handler (char *command)
 	(struct continuation_arg *) xmalloc (sizeof (struct continuation_arg));
       arg1->next = arg2;
       arg2->next = NULL;
-      arg1->data.integer = time_at_cmd_start;
-      arg2->data.integer = space_at_cmd_start;
+      arg1->data.longint = time_at_cmd_start;
+#ifdef HAVE_SBRK
+      arg2->data.longint = space_at_cmd_start;
+#endif
       add_continuation (command_line_handler_continuation, arg1);
     }

As far as the other warnings, I am not seeing them, what type of system are
you compiling on?

Elena



Mike Cleary writes:
 > Hello
 > I'm trying to report this error and I'm not sure if anybody knows about
 > this yet. Can somebody please tell me exactly what the error is.
 > I've pasted warnings below:
 > gcc -c -g -O2    -I. -I/home/buildsys/source/toolchain/gdb
 > -I/home/buildsys/sour
 > ce/toolchain/gdb/config -DHAVE_CONFIG_H
 > -I/home/buildsys/source/toolchain/gdb/..
 > /include/opcode -I/home/buildsys/source/toolchain/gdb/../readline/..
 > -I../bfd -I
 > /home/buildsys/source/toolchain/gdb/../bfd
 > -I/home/buildsys/source/toolchain/gd
 > b/../include -I../intl -I/home/buildsys/source/toolchain/gdb/../intl
 > -DMI_OUT=1
 >  -DGDBTK -DUI_OUT=1 -Wimplicit -Wreturn-type -Wcomment -Wtrigraphs
 > -Wformat -Wpa
 > rentheses -Wpointer-arith -Wuninitialized
 > /home/buildsys/source/toolchain/gdb/e
 > vent-top.c
 > /home/buildsys/source/toolchain/gdb/event-top.c: In function
 > `cli_command_loop':
 > /home/buildsys/source/toolchain/gdb/event-top.c:192: warning: implicit
 > declarati
 > on of function `strcat'
 > /home/buildsys/source/toolchain/gdb/event-top.c: In function
 > `command_handler':
 > /home/buildsys/source/toolchain/gdb/event-top.c:469: warning: implicit
 > declarati
 > on of function `isatty'
 > /home/buildsys/source/toolchain/gdb/event-top.c:518:
 > `space_at_cmd_start' undecl
 > ared (first use in this function)
 > /home/buildsys/source/toolchain/gdb/event-top.c:518: (Each undeclared
 > identifier
 >  is reported only once
 > /home/buildsys/source/toolchain/gdb/event-top.c:518: for each function
 > it appear
 > s in.)
 > /home/buildsys/source/toolchain/gdb/event-top.c: In function
 > `command_line_handl
 > er':
 > /home/buildsys/source/toolchain/gdb/event-top.c:709: warning: implicit
 > declarati
 > on of function `strncmp'
 > /home/buildsys/source/toolchain/gdb/event-top.c: In function
 > `async_disconnect':
 > /home/buildsys/source/toolchain/gdb/event-top.c:1019: warning: implicit
 > declarat
 > ion of function `getpid'
 > make[2]: *** [event-top.o] Error 1
 > make[2]: Leaving directory
 > `/home/buildsys/build/intel1/basic/native/toolchain/g
 > db'
 > make[1]: *** [all-gdb] Error 2
 > make[1]: Leaving directory
 > `/home/buildsys/build/intel1/basic/native/toolchain'
 > make: *** [bootstrap] Error 2
 > (END)
 >
 > If anybody could hlep that'd be great.
 > Thanks
 > -Mike

      parent reply	other threads:[~2002-06-21  2:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-20 13:08 Mike Cleary
2002-06-20 14:00 ` Jim Blandy
2002-06-20 14:48 ` Elena Zannoni
2002-06-20 16:32   ` Andrew Cagney
2002-06-21 17:13     ` *** [ser-tcp.o] Error 1 on alpha! Matthew H Bemis
2002-06-22 10:09       ` Andrew Cagney
2002-06-22 10:23         ` Matthew H Bemis
2002-06-26 20:28           ` Andrew Cagney
2002-06-20 19:16   ` Matthew H Bemis [this message]

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=DJEHKIJNENDCOJNKEBGKCEJFDFAA.bemis@iol.unh.edu \
    --to=bemis@iol.unh.edu \
    --cc=clp@iol.unh.edu \
    --cc=ezannoni@redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=mcleary@iol.unh.edu \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).