From: James Lemke <jim@TheLemkes.ca>
To: gdb@sources.redhat.com
Subject: strange behaviour -- gdbtk & stdin on winxp
Date: Fri, 15 Apr 2005 20:36:00 -0000 [thread overview]
Message-ID: <1113597409.18830.311.camel@keel.thelemkes.ca> (raw)
I did some searching on the archives but didn't find anything similar.
I'm using xscale-elf-insight.exe built from 6.1 sources, serially
connected to an xscale board. I'm debugging a simple program that reads
a string via fgets((char *)input_char, MAX_INPUT_LINE, stdin).
All works as expected with xscale-elf-gdb or xscale-elf-insight -nw.
But with the GUI, fgets() returns immediately with NULL, and errno set
to 9 (EBADF).
When built for a Linux host, xscale-elf-insight with and without -nw
work fine.
Does this problem sound familiar to anyone?
Jim.
--
James Lemke jim@TheLemkes.ca Orillia, Ontario
1992 ST1100, STOC #3750; FWD# M:245401 H:246889
Life is what happens while you're busy making other plans. --John Lennon
next reply other threads:[~2005-04-15 20:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-15 20:36 James Lemke [this message]
2005-04-15 20:50 ` Keith Seitz
2005-04-15 21:13 ` James Lemke
2005-04-18 14:55 ` James Lemke
2005-04-18 16:17 ` Dave Korn
2005-04-18 17:47 ` James Lemke
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=1113597409.18830.311.camel@keel.thelemkes.ca \
--to=jim@thelemkes.ca \
--cc=gdb@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