Please for help,
I have dump file from died application and want to exemine it with wd (
Watcom Debuger ). I am using :
wd -tr=pmd .dmp
but it does not gives me any hint how to examine it, how to find out where
and how the program died!?!?
Any help appreciated !
“Kostadin Vardin” <kvardin@rogers.com> wrote in message
news:dbr75i$m1l$1@inn.qnx.com…
Please for help,
I have dump file from died application and want to exemine it with wd (
Watcom Debuger ). I am using :
wd -tr=pmd .dmp
but it does not gives me any hint how to examine it, how to find out where
and how the program died!?!?
The cursor should be on the line that caused the crash. If it was compile
with debug mode, you should see the source, if not you are in assembler.
Any help appreciated !
Mario Charest wrote:
“Kostadin Vardin” <> kvardin@rogers.com> > wrote in message
news:dbr75i$m1l$> 1@inn.qnx.com> …Please for help,
I have dump file from died application and want to exemine it with wd (
Watcom Debuger ). I am using :
wd -tr=pmd .dmp
but it does not gives me any hint how to examine it, how to find out where
and how the program died!?!?The cursor should be on the line that caused the crash. If it was compile
with debug mode, you should see the source, if not you are in assembler.
Thanks Mario,
Actually this is a Photon application.All translation units I wrote in C
are compiled with debug mode. The cursor is in assembly code, having
“abmain” highlighted. I suppose this means the problem occured in abmain
?!?
Regards !
Any help appreciated !
“Kostadin Vardin” <kvardin@rogers.com> wrote in message
news:dbrm54$2v1$1@inn.qnx.com…
Mario Charest wrote:
“Kostadin Vardin” <> kvardin@rogers.com> > wrote in message
news:dbr75i$m1l$> 1@inn.qnx.com> …Please for help,
I have dump file from died application and want to exemine it with wd (
Watcom Debuger ). I am using :
wd -tr=pmd .dmp
but it does not gives me any hint how to examine it, how to find out
where
and how the program died!?!?The cursor should be on the line that caused the crash. If it was compile
with debug mode, you should see the source, if not you are in assembler.Thanks Mario,
Actually this is a Photon application.All translation units I wrote in C
are compiled with debug mode. The cursor is in assembly code, having
“abmain” highlighted. I suppose this means the problem occured in abmain
?!?
Yes, or some corruption occured before, that made abmain crashed.
This doesn’t sound like it’s going to be an easy one.
Regards !
Any help appreciated !
\
Yes, it really seems to be tough.
Sounds like the application gets hit by signal being in the main loop as
coded in abmain and causes the application to fail. I will need to dig
more, as this organizational part of the application was written before
me, I wrote the handlers on received messages. Any way on site the
application is observed with phditto from two stations and this sounds to
load Photon somehow.
Thanks Mario
Mario Charest wrote:
“Kostadin Vardin” <> kvardin@rogers.com> > wrote in message
news:dbrm54$2v1$> 1@inn.qnx.com> …
Mario Charest wrote:
“Kostadin Vardin” <> kvardin@rogers.com> > wrote in message
news:dbr75i$m1l$> 1@inn.qnx.com> …Please for help,
I have dump file from died application and want to exemine it with wd (
Watcom Debuger ). I am using :
wd -tr=pmd .dmp
but it does not gives me any hint how to examine it, how to find out
where
and how the program died!?!?The cursor should be on the line that caused the crash. If it was compile
with debug mode, you should see the source, if not you are in assembler.Thanks Mario,
Actually this is a Photon application.All translation units I wrote in C
are compiled with debug mode. The cursor is in assembly code, having
“abmain” highlighted. I suppose this means the problem occured in abmain
?!?Yes, or some corruption occured before, that made abmain crashed.
This doesn’t sound like it’s going to be an easy one.Regards !
Any help appreciated !
\
Yes
this was SIGALRM. I just added signal processing
function(PtAppAddSignalProc()) and it caugth this “friend”.
Interesting, it seems that some Ph library function is causing this (
wrapping Send itself ).
Kostadin Vardin wrote:
Yes, it really seems to be tough.
Sounds like the application gets hit by signal being in the main loop as
coded in abmain and causes the application to fail. I will need to dig
more, as this organizational part of the application was written before
me, I wrote the handlers on received messages. Any way on site the
application is observed with phditto from two stations and this sounds to
load Photon somehow.
Thanks MarioMario Charest wrote:
“Kostadin Vardin” <> kvardin@rogers.com> > wrote in message
news:dbrm54$2v1$> 1@inn.qnx.com> …
Mario Charest wrote:
“Kostadin Vardin” <> kvardin@rogers.com> > wrote in message
news:dbr75i$m1l$> 1@inn.qnx.com> …Please for help,
I have dump file from died application and want to exemine it with wd
(
Watcom Debuger ). I am using :
wd -tr=pmd .dmp
but it does not gives me any hint how to examine it, how to find out
where
and how the program died!?!?The cursor should be on the line that caused the crash. If it was
compile
with debug mode, you should see the source, if not you are in assembler.Thanks Mario,
Actually this is a Photon application.All translation units I wrote in C
are compiled with debug mode. The cursor is in assembly code, having
“abmain” highlighted. I suppose this means the problem occured in abmain
?!?Yes, or some corruption occured before, that made abmain crashed.
This doesn’t sound like it’s going to be an easy one.Regards !
Any help appreciated !
\
“Kostadin Vardin” <kvardin@rogers.com> wrote in message
news:dc3526$f1k$1@inn.qnx.com…
Yes
this was SIGALRM. I just added signal processing
function(PtAppAddSignalProc()) and it caugth this “friend”.
Interesting, it seems that some Ph library function is causing this (
wrapping Send itself ).To my knowledge none of the photon function can generate this alarm on their
own. Is it possible your code is using alarm() and you are not reseting it
properly with alarm(0) or you are getting hit by a timing window issue.
Kostadin Vardin wrote:
Yes, it really seems to be tough.
Sounds like the application gets hit by signal being in the main loop as
coded in abmain and causes the application to fail. I will need to dig
more, as this organizational part of the application was written before
me, I wrote the handlers on received messages. Any way on site the
application is observed with phditto from two stations and this sounds to
load Photon somehow.
Thanks MarioMario Charest wrote:
“Kostadin Vardin” <> kvardin@rogers.com> > wrote in message
news:dbrm54$2v1$> 1@inn.qnx.com> …
Mario Charest wrote:
“Kostadin Vardin” <> kvardin@rogers.com> > wrote in message
news:dbr75i$m1l$> 1@inn.qnx.com> …Please for help,
I have dump file from died application and want to exemine it with
wd
(
Watcom Debuger ). I am using :
wd -tr=pmd .dmp
but it does not gives me any hint how to examine it, how to find
out
where
and how the program died!?!?The cursor should be on the line that caused the crash. If it was
compile
with debug mode, you should see the source, if not you are in
assembler.Thanks Mario,
Actually this is a Photon application.All translation units I wrote
in C
are compiled with debug mode. The cursor is in assembly code, having
“abmain” highlighted. I suppose this means the problem occured in
abmain
?!?Yes, or some corruption occured before, that made abmain crashed.
This doesn’t sound like it’s going to be an easy one.Regards !
Any help appreciated !
\
I am always using :
alarm( 5 )
Send
alarm(0)
What do you mean by timing window issue ?
Mario Charest wrote:
“Kostadin Vardin” <> kvardin@rogers.com> > wrote in message
news:dc3526$f1k$> 1@inn.qnx.com> …
Yes
this was SIGALRM. I just added signal processing
function(PtAppAddSignalProc()) and it caugth this “friend”.
Interesting, it seems that some Ph library function is causing this (
wrapping Send itself ).To my knowledge none of the photon function can generate this alarm on their
own. Is it possible your code is using alarm() and you are not reseting it
properly with alarm(0) or you are getting hit by a timing window issue.
Kostadin Vardin wrote:Yes, it really seems to be tough.
Sounds like the application gets hit by signal being in the main loop as
coded in abmain and causes the application to fail. I will need to dig
more, as this organizational part of the application was written before
me, I wrote the handlers on received messages. Any way on site the
application is observed with phditto from two stations and this sounds to
load Photon somehow.
Thanks MarioMario Charest wrote:
“Kostadin Vardin” <> kvardin@rogers.com> > wrote in message
news:dbrm54$2v1$> 1@inn.qnx.com> …
Mario Charest wrote:
“Kostadin Vardin” <> kvardin@rogers.com> > wrote in message
news:dbr75i$m1l$> 1@inn.qnx.com> …Please for help,
I have dump file from died application and want to exemine it with
wd
(
Watcom Debuger ). I am using :
wd -tr=pmd .dmp
but it does not gives me any hint how to examine it, how to find
out
where
and how the program died!?!?The cursor should be on the line that caused the crash. If it was
compile
with debug mode, you should see the source, if not you are in
assembler.Thanks Mario,
Actually this is a Photon application.All translation units I wrote
in C
are compiled with debug mode. The cursor is in assembly code, having
“abmain” highlighted. I suppose this means the problem occured in
abmain
?!?Yes, or some corruption occured before, that made abmain crashed.
This doesn’t sound like it’s going to be an easy one.Regards !
Any help appreciated !
\
“Kostadin Vardin” <kvardin@rogers.com> wrote in message
news:dc3jur$p6g$1@inn.qnx.com…
I am always using :
alarm( 5 )
Send
alarm(0)What do you mean by timing window issue ?
In the example above, it’s possible that context switch occurs between the
Send() and the alarm(0) and that a higher priority process steal the CPU for
more then 5 seconds, hence you end up with an alarm even though the Send
took a few milliseconds.
It’s also possible (for whatever reason) that Send really takes 5 seconds.
Take out the alarm() calls as an experiment and see what happen.
Mario Charest wrote:
“Kostadin Vardin” <> kvardin@rogers.com> > wrote in message
news:dc3526$f1k$> 1@inn.qnx.com> …
Yes
this was SIGALRM. I just added signal processing
function(PtAppAddSignalProc()) and it caugth this “friend”.
Interesting, it seems that some Ph library function is causing this (
wrapping Send itself ).To my knowledge none of the photon function can generate this alarm on
their
own. Is it possible your code is using alarm() and you are not reseting
it
properly with alarm(0) or you are getting hit by a timing window issue.
Kostadin Vardin wrote:Yes, it really seems to be tough.
Sounds like the application gets hit by signal being in the main loop
as
coded in abmain and causes the application to fail. I will need to dig
more, as this organizational part of the application was written
before
me, I wrote the handlers on received messages. Any way on site the
application is observed with phditto from two stations and this sounds
to
load Photon somehow.
Thanks MarioMario Charest wrote:
“Kostadin Vardin” <> kvardin@rogers.com> > wrote in message
news:dbrm54$2v1$> 1@inn.qnx.com> …
Mario Charest wrote:
“Kostadin Vardin” <> kvardin@rogers.com> > wrote in message
news:dbr75i$m1l$> 1@inn.qnx.com> …Please for help,
I have dump file from died application and want to exemine it
with
wd
(
Watcom Debuger ). I am using :
wd -tr=pmd .dmp
but it does not gives me any hint how to examine it, how to
find
out
where
and how the program died!?!?The cursor should be on the line that caused the crash. If it was
compile
with debug mode, you should see the source, if not you are in
assembler.Thanks Mario,
Actually this is a Photon application.All translation units I
wrote
in C
are compiled with debug mode. The cursor is in assembly code,
having
“abmain” highlighted. I suppose this means the problem occured in
abmain
?!?Yes, or some corruption occured before, that made abmain crashed.
This doesn’t sound like it’s going to be an easy one.Regards !
Any help appreciated !
\
Thanks Mario,
That is exactly what happened!
BEST REGARDS !!
Mario Charest wrote:
“Kostadin Vardin” <> kvardin@rogers.com> > wrote in message
news:dc3jur$p6g$> 1@inn.qnx.com> …
I am always using :
alarm( 5 )
Send
alarm(0)What do you mean by timing window issue ?
In the example above, it’s possible that context switch occurs between the
Send() and the alarm(0) and that a higher priority process steal the CPU for
more then 5 seconds, hence you end up with an alarm even though the Send
took a few milliseconds.It’s also possible (for whatever reason) that Send really takes 5 seconds.
Take out the alarm() calls as an experiment and see what happen.
Mario Charest wrote:
“Kostadin Vardin” <> kvardin@rogers.com> > wrote in message
news:dc3526$f1k$> 1@inn.qnx.com> …
Yes
this was SIGALRM. I just added signal processing
function(PtAppAddSignalProc()) and it caugth this “friend”.
Interesting, it seems that some Ph library function is causing this (
wrapping Send itself ).To my knowledge none of the photon function can generate this alarm on
their
own. Is it possible your code is using alarm() and you are not reseting
it
properly with alarm(0) or you are getting hit by a timing window issue.
Kostadin Vardin wrote:Yes, it really seems to be tough.
Sounds like the application gets hit by signal being in the main loop
as
coded in abmain and causes the application to fail. I will need to dig
more, as this organizational part of the application was written
before
me, I wrote the handlers on received messages. Any way on site the
application is observed with phditto from two stations and this sounds
to
load Photon somehow.
Thanks MarioMario Charest wrote:
“Kostadin Vardin” <> kvardin@rogers.com> > wrote in message
news:dbrm54$2v1$> 1@inn.qnx.com> …
Mario Charest wrote:
“Kostadin Vardin” <> kvardin@rogers.com> > wrote in message
news:dbr75i$m1l$> 1@inn.qnx.com> …Please for help,
I have dump file from died application and want to exemine it
with
wd
(
Watcom Debuger ). I am using :
wd -tr=pmd .dmp
but it does not gives me any hint how to examine it, how to
find
out
where
and how the program died!?!?The cursor should be on the line that caused the crash. If it was
compile
with debug mode, you should see the source, if not you are in
assembler.Thanks Mario,
Actually this is a Photon application.All translation units I
wrote
in C
are compiled with debug mode. The cursor is in assembly code,
having
“abmain” highlighted. I suppose this means the problem occured in
abmain
?!?Yes, or some corruption occured before, that made abmain crashed.
This doesn’t sound like it’s going to be an easy one.Regards !
Any help appreciated !
\