Hello,
I’m trying to debug remotly an application using the Watcom debuger via
TCP/IP. When i start tcpserv on the remote host (where i’ve uploaded only
tcpserv) i have a
SIGSEGV at 0005:000056D7
Any thougths ?
Thanks for your answers.
Sebastien Cantos wrote:
Hello,
I’m trying to debug remotly an application using the Watcom debuger via
TCP/IP. When i start tcpserv on the remote host (where i’ve uploaded only
tcpserv) i have a
SIGSEGV at 0005:000056D7
Any thougths ?
Have you copied the /usr/watcom/10.6/wd directory to the target (what
you refer to as the “remote host”) ? You need these files. What I
typically do (since our targets don’t have a development system), when I
want to debug, is drop a copy of the files from the wd directory on
the target (along with a copy of tcpserv), and then run tcpserv in that
directory on the target (that way you don’t need to set paths and such).
I’ve copied all the directory /usr/watcom/10.6/wd to a directory on the
target host and put the tcpserv binary in that same directory. When i launch
tcpserv, there’s always the same problem (SIGSEGV). Maybe i need others
files from the watcom dir ? (there’s not a lot of space on the target box,
so i’ve to know exactly what files do i need).
Thanks for your answers.
Sebastien Cantos wrote:
Hello,
I’m trying to debug remotly an application using the Watcom debuger via
TCP/IP. When i start tcpserv on the remote host (where i’ve uploaded
only
tcpserv) i have a
SIGSEGV at 0005:000056D7
Any thougths ?Have you copied the /usr/watcom/10.6/wd directory to the target (what
you refer to as the “remote host”) ? You need these files. What I
typically do (since our targets don’t have a development system), when I
want to debug, is drop a copy of the files from the wd directory on
the target (along with a copy of tcpserv), and then run tcpserv in that
directory on the target (that way you don’t need to set paths and such).
\
Sebastien Cantos wrote:
I’ve copied all the directory /usr/watcom/10.6/wd to a directory on the
target host and put the tcpserv binary in that same directory. When i launch
tcpserv, there’s always the same problem (SIGSEGV). Maybe i need others
files from the watcom dir ? (there’s not a lot of space on the target box,
so i’ve to know exactly what files do i need).
Thanks for your answers.
Those should be all the files you need (and you probably don’t
need all of them, if things are really tight). I think your
SIGSEGV might be caused by some other problem.
Can you post a cksum of your tcpserv executable (preferably
- but not necessarily - performed on the target).
Mine (which works) is:
1490793611 25766 /bin/tcpserv
Rennie
Those should be all the files you need (and you probably don’t
need all of them, if things are really tight). I think your
SIGSEGV might be caused by some other problem.Can you post a cksum of your tcpserv executable (preferably
- but not necessarily - performed on the target).
Mine (which works) is:
1490793611 25766 /bin/tcpserv
Rennie
I’ve the same cksum as yours on the target. This problem seems realy
strange. I’m not an asm guru, but i’m going to try to disas something near
the segfault adresse to investigate …