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+NW+9XzSeNk3EzTIAnXC6vaBsH++MV+2QsTXuPG7 dTDm6pJShYex2n From: Juan Manuel Guerrero To: Eli Zaretskii Subject: Re: Difficulries with GDB 7.2 compiled with DJGPP Date: Sun, 16 Jan 2011 20:12:26 +0100 User-Agent: KMail/1.9.10 Cc: djgpp AT delorie DOT com References: <201101152018 DOT 51379 DOT juan DOT guerrero AT gmx DOT de> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <201101162012.26442.juan.guerrero@gmx.de> X-Y-GMX-Trusted: 0 Am Sonntag, 16. Januar 2011 schrieb Eli Zaretskii: > > From: Juan Manuel Guerrero > > Date: Sat, 15 Jan 2011 20:18:51 +0100 > > > > (gdb) b main > > Breakpoint 1 at 0x1f26: file 1.c, line 5. > > (gdb) r > > Starting program: f:/g/4/__bins__/bin/2.exe > > Don't know how to run. Try "help target". > > (gdb) target exec > > No executable file now. > > (gdb) > > > > > > Any suggestions? > > Can you debug the v2.04 build with GDB from the v2.03 build, and see > what causes the "Don't know how to run" message? The above error message is printed in find_default_run_target() in gdb/tagret.c. There, the struct target_ops is evaluated calling target_can_run(). For 2.03 version the following output is generated if I print the struct identifier string (a count = 1 means that target_can_run was successful): GNU gdb (GDB) 7.2 Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later 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=i586-pc-msdosdjgpp --target=djgpp". For bug reporting instructions, please see: ... Reading symbols from f:/g/3/__bins__/bin/1.exe...done. (gdb) b main Breakpoint 1 at 0x1f31: file 1.c, line 9. (gdb) r Starting program: f:/g/3/__bins__/bin/1.exe t->to_longname=djgpp target process: count=1 t->to_longname=Remote serial target in gdb-specific protocol: count=0 t->to_longname=Extended remote serial target in gdb-specific protocol: count=0 t->to_longname=Local trace dump file: count=0 t->to_longname=Local exec file: count=0 t->to_longname=Process record and replay target: count=0 t->to_longname=Process record and replay target: count=0 t->to_longname=djgpp target process: count=1 t->to_longname=Remote serial target in gdb-specific protocol: count=0 t->to_longname=Extended remote serial target in gdb-specific protocol: count=0 t->to_longname=Local trace dump file: count=0 t->to_longname=Local exec file: count=0 t->to_longname=Process record and replay target: count=0 t->to_longname=Process record and replay target: count=0 t->to_longname=djgpp target process: count=1 t->to_longname=Remote serial target in gdb-specific protocol: count=0 t->to_longname=Extended remote serial target in gdb-specific protocol: count=0 t->to_longname=Local trace dump file: count=0 t->to_longname=Local exec file: count=0 t->to_longname=Process record and replay target: count=0 t->to_longname=Process record and replay target: count=0 Breakpoint 1, main () at 1.c:9 9 printf("i=%d", i); (gdb) q A debugging session is active. Inferior 1 [process 42] will be killed. Quit anyway? (y or n) For the 2 2.04 version the following output is printed: GNU gdb (GDB) 7.2 Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later 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: ... Reading symbols from f:/g/4/__bins__/bin/1.exe...done. (gdb) b main Breakpoint 1 at 0x1f31: file 1.c, line 9. (gdb) r Starting program: f:/g/4/__bins__/bin/1.exe t->to_longname=Remote serial target in gdb-specific protocol: count=0 t->to_longname=Extended remote serial target in gdb-specific protocol: count=0 t->to_longname=Local trace dump file: count=0 t->to_longname=Local exec file: count=0 t->to_longname=Process record and replay target: count=0 t->to_longname=Process record and replay target: count=0 (gdb) q As can be seen the "djgpp target process" does not appear the struct. May be that the configuration process is wrong. More investigation needs to be done. Regards, Juan M. Guerrer0