From: "Shelby Cain" <scain1@austin.rr.com>
To: "cygwin" <cygwin@sources.redhat.com>
Subject: Greetings...
Date: Thu, 28 Sep 2000 16:20:00 -0000 [thread overview]
Message-ID: <005301c029a2$c74b1040$1605a018@austin.rr.com> (raw)
Hello all -- I'm new to the list and I have a question that I'm sure has
been asked many times before. I'm used to using tools like gcc, gdb, make,
etc in a mixed environment of Solaris and Linux.
My problem is taking a simple program like so:
int main()
{
char * foo = 0;
crashme(foo);
}
int crashme(char * cp);
{
strcpy(cp, "KABOOM!!");
}
and compiling and linking it via -g using cygwin produces an executable that
does not produce a core file when it crashes. One might suggest that
running it via gdb (ie: gdb crashme.exe) will allow me to catch the
offending statement... however I would really prefer a core file to work
with as I don't have to "recreate" the situation in order to see what is
going on.
Even when I use gdb to catch the seg fault... the stack window isn't
providing me with any useful information. When I open up the gdb console
and try "backtrace" I get something to the effect of:
"Error: #0 0x61070850 in _size_of_stack_reserve__ ()
Cannot access memory at address 0x2000000"
Normally I would expect the backtrace to produce something meaningful like:
#0 0xef6a4644 in strcpy () from /usr/lib/libc.so.1
#1 0x10598 in crashme (cp=0x0) at test.c:9
#2 0x10574 in main () at test.c:4
Could anyone explain this to me outright or point me towards a FAQ?
Regards,
Shelby Cain
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next reply other threads:[~2000-09-28 16:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-28 16:20 Shelby Cain [this message]
2000-10-03 12:47 ` Problems in using gdb to catch the seg fault (was: Re: Greetings...) Andreas Eibach
2018-10-17 20:09 Greetings Mr. Kofi Adomakoh
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='005301c029a2$c74b1040$1605a018@austin.rr.com' \
--to=scain1@austin.rr.com \
--cc=cygwin@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).