Hi there!
I’m trying to debug a series of network drivers using the mometics IDE.
I’m using 6.2a (PE) but am having no luck.
I can debug standard “c” applications without any problems but when
trying to get the IDE to debug io-net I get the following symptoms
a,
Completely locks the machine (Running a first instance io-net seems to
fix this)
b,
Remotely debugging appears to work, however I cannot get the IDE to
display any information about my driver (even though it is compiled and
run with the debug option)
c,
I’ve managed to get the IDE to run with io-net_g using a command line
option of “-d mydriver.so”. This appears to load OK but when I try to
run debug I get the following message:
“io-net_g ThreadCtrl: Operation not permitted”
Is this due to the debugger not running as root? If so how do I get the
debugger to run as root?
Regards
Dave Edwards
A further addition to this is that I can run the profiler from the IDE.
However I cannot get the profiler to resolve the symbols for the loaded
drivers
Any suggestions?
Dave
Dave Edwards wrote:
Hi there!
I’m trying to debug a series of network drivers using the mometics IDE.
I’m using 6.2a (PE) but am having no luck.
I can debug standard “c” applications without any problems but when
trying to get the IDE to debug io-net I get the following symptoms
a,
Completely locks the machine (Running a first instance io-net seems to
fix this)
b,
Remotely debugging appears to work, however I cannot get the IDE to
display any information about my driver (even though it is compiled and
run with the debug option)
c,
I’ve managed to get the IDE to run with io-net_g using a command line
option of “-d mydriver.so”. This appears to load OK but when I try to
run debug I get the following message:
“io-net_g ThreadCtrl: Operation not permitted”
Is this due to the debugger not running as root? If so how do I get the
debugger to run as root?
Regards
Dave Edwards
It could be that the IDE uses sockets to work(I know for sure that DDD in
6.1 uses sockets) and therefore when you stop the io-net process the process
also stops(Which explains why you are able to do remote debugging).I guess
it is just not designed to be used for debugging io-net.I got tired of
trying to get DDD to debug io-net and have stuck to classic command line
Gdb.
Hope that helps.
Sreekanth
“Dave Edwards” <Dave.edwards@abicom-international.com> wrote in message
news:3DCA8D86.9090204@abicom-international.com…
A further addition to this is that I can run the profiler from the IDE.
However I cannot get the profiler to resolve the symbols for the loaded
drivers
Any suggestions?
Dave
Dave Edwards wrote:
Hi there!
I’m trying to debug a series of network drivers using the mometics IDE.
I’m using 6.2a (PE) but am having no luck.
I can debug standard “c” applications without any problems but when
trying to get the IDE to debug io-net I get the following symptoms
a,
Completely locks the machine (Running a first instance io-net seems to
fix this)
b,
Remotely debugging appears to work, however I cannot get the IDE to
display any information about my driver (even though it is compiled and
run with the debug option)
c,
I’ve managed to get the IDE to run with io-net_g using a command line
option of “-d mydriver.so”. This appears to load OK but when I try to
run debug I get the following message:
“io-net_g ThreadCtrl: Operation not permitted”
Is this due to the debugger not running as root? If so how do I get the
debugger to run as root?
Regards
Dave Edwards