Mail Archives: djgpp/2011/05/23/14:52:17
X-Authentication-Warning: | delorie.com: mail set sender to djgpp-bounces using -f
|
X-Recipient: | djgpp AT delorie DOT com
|
X-Authenticated: | #27081556
|
X-Provags-ID: | V01U2FsdGVkX1+yK4wROFuyG1ujrE4VzTDUwLrcgg0whYWTot+TpE
|
| lDWn7FrS4fD6y8
|
From: | Juan Manuel Guerrero <juan DOT guerrero AT gmx DOT de>
|
To: | djgpp AT delorie DOT com
|
Subject: | Re: gdb doesn't work on windows
|
Date: | Mon, 23 May 2011 20:26:48 +0200
|
User-Agent: | KMail/1.9.10
|
MIME-Version: | 1.0
|
Message-Id: | <201105232026.48501.juan.guerrero@gmx.de>
|
X-Y-GMX-Trusted: | 0
|
Jim Michaels <jmichae3 AT yahoo DOT com> wrote:
> the curses library that gdb is using doesn't work on windows XP's
> cmd.exe or windows command.com.
> I don't like curses. ncurses (no curses) works much better, however,
> I am not the author.
The use of any kind of curses has no impact in gdb.exe.
Only if gdbtui is compiled then some kind of curses library is required.
The port contains both versions of versions of gdb so you are free to choose
the one you prefer.
> what I essentially get with all djgpp products is a temporary 50-line
> mode (all my consoles have 9999 lines and 80 or 132 columns). within
> that temporary 50-line mode while the djgpp program runs, with gdb I
> get a gdb line at the bottom of the console and the cursor at the
> center left. if I press enter, the gdb line appears where the cursor
> was. once in a while, I get 2 gdb lines during my debugging session,
> which essentially consists of:
OFYI, at least for me the port of gdb-7.2 works flawlessly. I use it for all
DJGPP projects and I have never experienced the difficulties you are describing.
My console settings are always 80 cols by 5000 rows and a tipical gdbtui
session looks like below. It produces like almost all DJGPP aplications
its 50 line mode output.
OFYI, all zip files for my DJGPP installation are always downloaded from
different DJGPP mirrors so I am quite sure that the ports I do upload really
work as expected and that I use the same programs than the DJGPP user does.
If something would be broken with gdb72br2 I thing I would have noted it.
Regards,
Juan M. Guerrero
+--test.c-------------------------------------------------------------------+
|3942 |
|3943 #undef TEST_TYPE |
|3944 } |
|3945 |
|3946 |
|3947 void long_double_math_function_test(FILE *out) |
|3948 { |
|3949 } |
|3950 |
|3951 |
|3952 int main(void) |
|3953 { |
|3954 FILE *out; |
|3955 |
B+>|3956 out = fopen("test.txt", "w"); |
|3957 if (out == NULL) |
|3958 { |
|3959 printf("Can not open test.txt. Test failed.\n"); |
|3960 return 1; |
|3961 } |
|3962 |
|3963 printf("Testing:\n" |
|3964 " printf family of functions...\n"); |
|3965 flags_test(out); |
|3966 length_modifiers_test(out); |
|3967 numeric_conversion_specifiers_test(out); |
|3968 printf_test(out); |
|3969 |
|3970 printf(" signbit...\n"); |
|3971 signbit_test(out); |
|3972 |
+---------------------------------------------------------------------------+
djgpp process 42 In: main Line: 3956 PC: 0x29311
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "--host=i786-pc-msdosdjgpp --target=djgpp".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from f:/ls/srcs/contrib/libsupp-6.5/tests/test.exe...done.
(gdb) b main
Breakpoint 1 at 0x29311: file test.c, line 3956.
(gdb) r
Starting program: f:/ls/srcs/contrib/libsupp-6.5/tests/test.exe
Breakpoint 1, main () at test.c:3956
(gdb)
- Raw text -