From: Brad Lucier <lucier@math.purdue.edu>
To: binutils@sourceware.cygnus.com, lucier@math.purdue.edu
Cc: staff@math.purdue.edu, wilker@math.purdue.edu
Subject: Re: alpha linux fix for gprof
Date: Fri, 06 Aug 1999 10:00:00 -0000 [thread overview]
Message-ID: <199908061659.LAA00484@polya.math.purdue.edu> (raw)
>
> gprof from binutils.2.9.5.04 was dumping core with glibc2.1.1, kernel 2.2.10,
> gcc-2.95.
>
> When building it I got the following message:
>
> ../../gprof/corefile.c:728: warning: int format, different type arg (arg 2)
>
> The following change seemed to fix the problem:
>
Sorry, I should have been more careful; now it doesn't dump core, but
it gives me nonsense answers when trying to profile gcc-2.95.
At any rate, the following change gets rid of the error message.
===================================================================
RCS file: RCS/corefile.c,v
retrieving revision 1.1
diff -c -r1.1 corefile.c
*** corefile.c 1999/08/06 15:30:23 1.1
--- corefile.c 1999/08/06 16:39:13
***************
*** 723,730 ****
discard_underscores = 0;
}
! DBG (AOUTDEBUG, printf ("[core_create_line_syms] %d %s 0x%lx\n",
! ltab.limit - ltab.base, ltab.limit->name,
(unsigned long) ltab.limit->addr));
++ltab.limit;
}
--- 723,730 ----
discard_underscores = 0;
}
! DBG (AOUTDEBUG, printf ("[core_create_line_syms] %ld %s 0x%lx\n",
! (unsigned long)(ltab.limit - ltab.base), ltab.limit->name,
(unsigned long) ltab.limit->addr));
++ltab.limit;
}
Brad Lucier lucier@math.purdue.edu
next reply other threads:[~1999-08-06 10:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-06 10:00 Brad Lucier [this message]
1999-08-06 11:59 ` Ian Lance Taylor
-- strict thread matches above, loose matches on Subject: below --
1999-08-06 9:14 Brad Lucier
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=199908061659.LAA00484@polya.math.purdue.edu \
--to=lucier@math.purdue.edu \
--cc=binutils@sourceware.cygnus.com \
--cc=staff@math.purdue.edu \
--cc=wilker@math.purdue.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).