problems with gdb/ddd

QNX Newsgroups (Archives) qdn.public.qnxrtp.devtools
#1

Hello,

Porting fuzz I have got couple of problems. gdb is showing :

Type “show copying” to see the conditions.
There is absolutely no warranty for GDB. Type “show warranty” for
details.
This GDB was configured as “i386-qnx”…
(gdb)
(gdb)
(gdb) list
101 int argc;
102 char *argv;
103 {
104 float f;
105
106 /
107 * Parse command line
108 /
109 while ((++argv) != NULL)
110 if (*argv != SWITCH) { / Not a switch, must be
a
lengt
h */
(gdb) break 109
Breakpoint 1 at 0x804874c: file fuzz.c, line 109.
(gdb) run
Starting program: fuzz
Launching on pty /dev/ptyp2
Debug server launched.
Remote (spawn error): No such file or directory.
(gdb)


And that’s it. I can’t debug anything at all. This was in my Toshiba
Laptop.
anyway building the bin is ok but with couple of warnings which I must
correct. But when I am trying to run the program just garbage comes on
screen … and that’s it. the pterm then is messed up with wrong chars
…
My program reads from $ a command line arguments. If it is NULL then
show usage(). as a normal way. Instead of my usage it comes just trash
…

Using file to make sure I have a correct bin produced it is said:

$ file fuzz
fuzz: ELF 32-bit LSB executable, Intel 80386, version 1, dynamically
linked
(uses shared libs), not stripped


stef

#2

the garbage came from that random generator number … but anyway the
gdb is not working still.
brr.

Stefan Parvu wrote:

Hello,

Porting fuzz I have got couple of problems. gdb is showing :

Type “show copying” to see the conditions.
There is absolutely no warranty for GDB. Type “show warranty” for
details.
This GDB was configured as “i386-qnx”…
(gdb)
(gdb)
(gdb) list
101 int argc;
102 char *argv;
103 {
104 float f;
105
106 /
107 * Parse command line
108 /
109 while ((++argv) != NULL)
110 if (*argv != SWITCH) { / Not a switch, must be
a
lengt
h */
(gdb) break 109
Breakpoint 1 at 0x804874c: file fuzz.c, line 109.
(gdb) run
Starting program: fuzz
Launching on pty /dev/ptyp2
Debug server launched.
Remote (spawn error): No such file or directory.
(gdb)

And that’s it. I can’t debug anything at all. This was in my Toshiba
Laptop.
anyway building the bin is ok but with couple of warnings which I must
correct. But when I am trying to run the program just garbage comes on
screen … and that’s it. the pterm then is messed up with wrong chars
…
My program reads from $ a command line arguments. If it is NULL then
show usage(). as a normal way. Instead of my usage it comes just trash
…

Using file to make sure I have a correct bin produced it is said:

$ file fuzz
fuzz: ELF 32-bit LSB executable, Intel 80386, version 1, dynamically
linked
(uses shared libs), not stripped

stef

#3

and the gdb should be setup for target as the docs says. … Ahhh
Now I am reading it … But why is like this ?
Setting the target !


Stefan Parvu wrote:

the garbage came from that random generator number … but anyway the
gdb is not working still.
brr.

Stefan Parvu wrote:

Hello,

Porting fuzz I have got couple of problems. gdb is showing :

Type “show copying” to see the conditions.
There is absolutely no warranty for GDB. Type “show warranty” for
details.
This GDB was configured as “i386-qnx”…
(gdb)
(gdb)
(gdb) list
101 int argc;
102 char *argv;
103 {
104 float f;
105
106 /
107 * Parse command line
108 /
109 while ((++argv) != NULL)
110 if (*argv != SWITCH) { / Not a switch, must be
a
lengt
h */
(gdb) break 109
Breakpoint 1 at 0x804874c: file fuzz.c, line 109.
(gdb) run
Starting program: fuzz
Launching on pty /dev/ptyp2
Debug server launched.
Remote (spawn error): No such file or directory.
(gdb)

And that’s it. I can’t debug anything at all. This was in my Toshiba
Laptop.
anyway building the bin is ok but with couple of warnings which I must
correct. But when I am trying to run the program just garbage comes on
screen … and that’s it. the pterm then is messed up with wrong chars
…
My program reads from $ a command line arguments. If it is NULL then
show usage(). as a normal way. Instead of my usage it comes just trash
…

Using file to make sure I have a correct bin produced it is said:

$ file fuzz
fuzz: ELF 32-bit LSB executable, Intel 80386, version 1, dynamically
linked
(uses shared libs), not stripped

stef

#4

The problem is not that you aren’t setting the target - that is done
by default now, but that you aren’t specifying the path for your
program correctly.

You need to do gdb ./fuzz

Stefan Parvu <sparvu@cc.hut.fi> wrote:

and the gdb should be setup for target as the docs says. … Ahhh
Now I am reading it … But why is like this ?
Setting the target !



Stefan Parvu wrote:

the garbage came from that random generator number … but anyway the
gdb is not working still.
brr.

Stefan Parvu wrote:

Hello,

Porting fuzz I have got couple of problems. gdb is showing :

Type “show copying” to see the conditions.
There is absolutely no warranty for GDB. Type “show warranty” for
details.
This GDB was configured as “i386-qnx”…
(gdb)
(gdb)
(gdb) list
101 int argc;
102 char *argv;
103 {
104 float f;
105
106 /
107 * Parse command line
108 /
109 while ((++argv) != NULL)
110 if (*argv != SWITCH) { / Not a switch, must be
a
lengt
h */
(gdb) break 109
Breakpoint 1 at 0x804874c: file fuzz.c, line 109.
(gdb) run
Starting program: fuzz
Launching on pty /dev/ptyp2
Debug server launched.
Remote (spawn error): No such file or directory.
(gdb)

And that’s it. I can’t debug anything at all. This was in my Toshiba
Laptop.
anyway building the bin is ok but with couple of warnings which I must
correct. But when I am trying to run the program just garbage comes on
screen … and that’s it. the pterm then is messed up with wrong chars
…
My program reads from $ a command line arguments. If it is NULL then
show usage(). as a normal way. Instead of my usage it comes just trash
…

Using file to make sure I have a correct bin produced it is said:

$ file fuzz
fuzz: ELF 32-bit LSB executable, Intel 80386, version 1, dynamically
linked
(uses shared libs), not stripped

stef

–
cburgess@qnx.com