From: Andrew Haley <aph@redhat.com>
To: "Vivek Katakam" <vivek1717@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Reg SEGV
Date: Fri, 12 May 2006 14:47:00 -0000 [thread overview]
Message-ID: <17508.55314.422427.817105@dell.pink> (raw)
In-Reply-To: <d0e0ce060605120744w235c86a6j51894f58daa97316@mail.gmail.com>
Vivek Katakam writes:
>
> I am recieving segmentation fault at the following line :
> vfprintf(output_file, input_msg, allargs);
>
> when run in gdb I am getting this:
> 847 vfprintf(output_file, input_msg, allargs);
> (gdb) p output_file
> $1 = (FILE *) 0x504750
> (gdb) p input_msg
> $2 = 0x2a9588fdc8 "schema to %s: %d %*s\n"
> (gdb) p allargs
> $3 = {{gp_offset = 48, fp_offset = 48, overflow_arg_area = 0x7fbffb2428,
> reg_save_area = 0x7fbffb2350}}
> (gdb)
>
> I want to know what is wrong with the code.
We don't know because you didn't post the code. Post the code and
we'll tell you.
Andrew.
next prev parent reply other threads:[~2006-05-12 14:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-12 14:44 Vivek Katakam
2006-05-12 14:47 ` Andrew Haley [this message]
2006-05-12 14:53 ` John Love-Jensen
2006-05-13 9:50 ` Vivek Katakam
2006-05-13 10:06 ` Andrew Haley
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=17508.55314.422427.817105@dell.pink \
--to=aph@redhat.com \
--cc=gcc-help@gcc.gnu.org \
--cc=vivek1717@gmail.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).