gcc profiling broken?
- From: andrew_terekhov@xxxxxxxxx
- Date: Tue, 23 Oct 2007 17:23:38 -0700 (PDT)
A simple program like this:
#include <stdio.h>
int main(int argc, char* argv[])
{
printf("Hello, world!\n");
printf("argc: %d\n", argc);
return 0;
}
when compiled with profiling:
gcc -pg -g hello.c -o hello
dumps core:
Starting program: /home/andrew/dev/kmv/components/tests/prof/cee/hello
Hello, world!
Program received signal SIGSEGV, Segmentation fault.
main (argc=Error accessing memory address 0x19: Bad address.
) at hello.c:7
7 printf("argc: %d\n", argc);
I run i386 7 beta1 from yesterday.
gcc -v
Using built-in specs.
Target: i386-undermydesk-freebsd
Configured with: FreeBSD/i386 system compiler
Thread model: posix
gcc version 4.2.1 20070719 [FreeBSD]
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: gcc profiling broken?
- From: Bruce Cran
- Re: gcc profiling broken?
- Prev by Date: MAC Framework KPI changes on the way in 8-CURRENT
- Next by Date: Re: [ANN] 8-CURRENT, RELENG_7 and RELENG_6 have gotten latest unionfs improvements
- Previous by thread: MAC Framework KPI changes on the way in 8-CURRENT
- Next by thread: Re: gcc profiling broken?
- Index(es):
Relevant Pages
|
