From: Fernando Nasser <fnasser@cygnus.com>
To: Fabrice Gautier <Fabrice_Gautier@sdesigns.com>
Cc: "'insight@sources.redhat.com'" <insight@sources.redhat.com>,
"GDB (E-mail)" <gdb@sourceware.cygnus.com>
Subject: Re: Buil problem
Date: Mon, 20 Nov 2000 16:39:00 -0000 [thread overview]
Message-ID: <3A19C413.519904F1@cygnus.com> (raw)
In-Reply-To: <B1F6452C89AFD411AE0800A0CC734C23015032@EMAIL1>
This fix is already in the current sources. It was broken for a few hours
and it is very unfortunate you've got it during that window of time.
I inadvertently broke this when splitting a file so at least you have
someone to blame ;-)
BTW, when using the latest sources from cvs and encountering a build problem,
always try to do a "cvs update". Any glitch like this is normally fixed
quickly.
Sorry about all the trouble.
Fernando
Fabrice Gautier wrote:
>
> Hi,
>
> I think i found why it failed. The following patch seems to have a good
> effect:
>
> --- gdb/linespec.c~ Fri Nov 10 15:02:56 2000
> +++ gdb/linespec.c Mon Nov 20 15:13:43 2000
> @@ -37,7 +37,7 @@
>
> extern char *operator_chars (char *, char **);
>
> -extern char *no_symtab_msg;
> +extern char no_symtab_msg[];
>
> /* Prototypes for local functions */
>
> The no_symtab_msg is defined as char no_symtab_msg[] in an other file, and
> not as
> char *no_symtab_msg.
>
> I think there might be a few other place where this mistake could have been
> made but i didn't saw any around that one.
>
> By the way this seems more like a gdb thing than a insight thing, but it was
> somehow triggered when using the gui.
>
> Thanks
>
> > -----Original Message-----
> > From: Fabrice Gautier [ mailto:Fabrice_Gautier@sdesigns.com ]
> > Sent: Monday, November 20, 2000 2:19 PM
> > To: 'insight@sources.redhat.com'
> > Subject: RE: Buil problem
> >
> >
> > Hi,
> >
> > Attached is a call stack I obtained with gdb,
> >
> > If it helps find the problem.
> >
> > Thanks
> >
> > > -----Original Message-----
> > > From: Fabrice Gautier [ mailto:Fabrice_Gautier@sdesigns.com ]
> > > Subject: RE: Buil problem
> > >
> > >
> > > Using the latest snapshot i didn't have any problem building.
> > > But insight
> > > still crash unless I use -nw.
> > >
> > > Thanks
> >
> >
> >
--
Fernando Nasser
Red Hat Canada Ltd. E-Mail: fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario M4P 2C9
next prev parent reply other threads:[~2000-11-20 16:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-20 16:12 Fabrice Gautier
2000-11-20 16:39 ` Fernando Nasser [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-11-20 19:09 Fabrice Gautier
2000-11-20 18:22 Fabrice Gautier
2000-11-20 18:56 ` Christopher Faylor
2000-11-20 19:10 ` Fernando Nasser
2000-11-20 14:19 Fabrice Gautier
2000-11-20 14:05 Fabrice Gautier
2000-11-20 10:55 Fabrice Gautier
2000-11-17 12:34 Fabrice Gautier
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=3A19C413.519904F1@cygnus.com \
--to=fnasser@cygnus.com \
--cc=Fabrice_Gautier@sdesigns.com \
--cc=gdb@sourceware.cygnus.com \
--cc=insight@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).