FDK + crashing in FM8

Thread View: adobe.framemaker

8 messages

[T] Back to Threads [V] Tree View [G] Group Articles

8 total messages Started by Peter_Hanzel Mon, 22 Sep 2008 10:24

#2293

Author: Peter_Hanzel
Date: Mon, 22 Sep 2008 10:24

10 lines
1158 bytes

Hello.

We have an application plugin for FrameMaker. We have used in FM5.5.6, FM7 and stability is quite good. We have compiled this plugin using FDK8 and use it in FrameMaker 8. And here comes the problem.
Stability is very pure.
We reveice FrameMaker internal error and FM crashes.

My question is how to debug this to know what caused FM internal error.
The FM crash cccurs almost every where (open FN document, add text and so on.) But this is totaly unexpected. So sometime it goes through, some times not.

Thanks for any suggestions.

Re: FDK + crashing in FM8

#2294

Author: Peter_Hanzel
Date: Mon, 22 Sep 2008 11:31

6 lines
788 bytes

Most error we get is this:

Internal Error: 8004, 7759766, 4845196, 6838291
FrameMaker 8.0.0 for Intel
Build: 8.0p277
Window System: MSWindows

Re: FDK + crashing in FM8

#2295

Author: Russ Ward
Date: Mon, 22 Sep 2008 13:02

5 lines
783 bytes

Hi Peter,

Have you tried using the Visual Studio debugger? I would think that is the best option, if you can duplicate the crash while debugging.

Russ

Re: FDK + crashing in FM8

#2299

Author: Peter_Hanzel
Date: Mon, 22 Sep 2008 15:06

3 lines
865 bytes

Hello.

This is problem. We are debuging it in Visual Studio, but this Internal Error throws no exception so I don't know how to stop it there. It simply displays FrameMaker has detected internal error and debugging stops.

Re: FDK + crashing in FM8

#2302

Author: Scott_Prentice
Date: Mon, 22 Sep 2008 16:00

5 lines
1196 bytes

Hi Peter...

I find the best way to locate the cause of these errors is to add debugging F_Printf() messages (sequentially numbered) to the code so you can determine exactly the line that's causing the problem. Start with the F_Printf()s spread out, then as you see the general location, add them more specifically and you'll be able to locate the problem. Typically, it's a variable that's not freed or one that is freed but shouldn't be. I've seen this sort of thing happen between releases or FDK versions or compiler versions as well.

...scott

Re: FDK + crashing in FM8

#2306

Author: Russ Ward
Date: Mon, 22 Sep 2008 17:21

3 lines
1084 bytes

Scott, shouldn't you be able to see this in the debugger too? I guess I don't quite understand... it seems that if the crash is being caused by the API client in the debugger, you would have to be able to follow the code line by line until it crashes. If Frame crashes without invoking the active debugger, wouldn't this indicate that something else is causing the crash, not the API client in question?

Russ

Re: FDK + crashing in FM8

#2307

Author: Scott_Prentice
Date: Mon, 22 Sep 2008 17:55

5 lines
1040 bytes

Hi Russ .. yes, it *should* show up in the debugger as well. I've just seen cases where the debugger doesn't show what I think it should, and was offering this as an alternative method. It does sound like the problem is being caused by something outside the scope of the API client, which the debugger may not be able to trap, but an F_Printf() call may show where that location is.

Cheers,

...scott

Re: FDK + crashing in FM8

#1968

Author: Peter_Hanzel
Date: Thu, 16 Oct 2008 17:03

10 lines
1107 bytes

Hello.

I have set Visual Studio to break on Windows exception 0xC0000005.
And this is exactly causing FrameMaker to crash.

So I checked stack trace and then used continue and it showed FrameMaker internal error 8004.

As I cheched stack trace. It was deeply in assembly inside FrameMaker, but just after return from F_ApiNotify. So our F_ApiNotify callback ends succesfully without exceptions, but after processing this event, it crashed inside FrameMaker.

Any suggestions what to do more?

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads