PB 11.5 Latest EBF Issues

[Randy]

After installing the latest EBF, my win32 applications blowup randomly
at the same 2 memory locations in PBSHR115.dll. This occurs when I open
a window and before it is painted, but I cannot isolate it. When I use
the debugger and step through the code, it works. If I turn on Trace,
the trace file is not closed when the application terminates so it is
not usable.

I un-installed PB11.5 and re-installed. The original release, build
2506, is OK. I applied the next EBF, and it works OK. Then applied the
latest ebf, it fails again.

So, my questions:

Anyone else having problems like this?

What is PBSHR115.dll doing? If I had a clue then perhaps I would be able
to look somewhere.

TIA
Randy

[Terry Voth [TeamSybase]]

To do a trace on a crash, you need to use a PBDEBUG trace, not a
profiling trace. Only profiling trace files will be unusable if the
application crashes.

This and other suggestions on dealing with crashes are listed at the
Troubleshooting Guide on my site (see below).

Good luck,

Terry and Sequel the techno-kitten

On 26 Feb 2009 08:44:59 -0800, Randy <CGreenwellAtsparusaDotcom>
wrote:

*********************************
Build your vocabulary while feeding the hungry
http://www.freerice.com
*********************************
Newsgroup User Manual
=====================
TeamSybase <> Sybase employee
Forums = Peer-to-peer
Forums <> Communication with Sybase
IsNull (AnswerTo (Posting)) can return TRUE
Forums.Moderated = TRUE, so behave or be deleted
*********************************

Sequel's Sandbox: http://www.techno-kitten.com
Home of PBL Peeper, a free PowerBuilder Developer's Toolkit.
Version 4.0.4 now available at the Sandbox
PB Futures updated June 25/2008
See the PB Troubleshooting & Migration Guides at the Sandbox
^ ^
o o
=*=

[Randy]

Terry, thanks for reminding me about PBDebug. I had completely
forgotten about it. It may be related to age but don't tell my girl friend.

Anyway... Here is my problem. Now what to do about it. I guess I need
to submit a bug report since it doesn't look like something in my code.

W_PROJECTS is a sheet in a MDI frame with a datawindow on it.
_________________________________
End class function +CREATE for class W_PROJECTS, lib entry W_PROJECTS
******Latest EBF blows up here**********

*******These are the next lines after the end of the Create when running
earlier EBF.
Executing object function +CREATE for class DWOBJECT, lib entry _TYPEDEF
End object function +CREATE for class DWOBJECT, lib entry _TYPEDEF
_________________________________

To me, this implies that the base class, DWOBJECT, failed to be created.
Nes Pas?

Randy

[Terry Voth [TeamSybase]]

I'd probably start looking at the DataWindows assigned to controls on
that window. Start swapping out drop-dead simple DataWindows for what
you've got. If you can narrow it down to a DataWindow object, then
you've narrowed your scope considerably, although you're probably
stuck without diagnostic tools. If that's where you are, then if
nothing raises your suspicions from a code review, you might be left
with deleting controls until you get it to work, then examine the
last-deleted control.

One thing to think about when code reviewing a DW is the expressions.
PBL Peeper has a report that lists DW expressions. (At least I think
the public version has that report; if not, drop me an email for a
link to the latest and greatest and most unstable. <g>) Bad
expressions can easily bring a DW down.

Good luck,

Terry and Sequel the techno-kitten

On 26 Feb 2009 10:53:12 -0800, Randy <CGreenwellAtsparusaDotcom>
wrote:

[Randy]

Thanks Terry. I narrowed it down to the RT Edit style on columns.
Changing the edit style to Edit instead of Rich Text and the problem
goes away. I now need to make sure that all of my dlls are right for
this EBF before I call tech support.

This is a shame because that is why I installed the EBF, to use the RT
Edit style.

[Jeff Gibson]

Randy,

Please post your bug to case express. We are a few weeks out from moving
our application from PB10 to PB11.5 specifically so we can use the new Rich
Text Edit Style.

Is it just that you turned the column style on, or were you trying to do
something specific to the column?

TIA

Jeff Gibson
Intercept Solutions - Sybase SQL Anywhere OEM Partner
Nashville, TN

"Randy" <CGreenwellAtsparusaDotcom> wrote in message
news:49a80c77@forums-1-dub...

[Randy]

Jeff,

For us, the error occurs when the DWOBJECT is created. It only happens
on tab pages. In fact it only happens when you dynamically create the
tab page from a UO which has a DW UO on it.

I have not reported the case yet because I am still trying to build a
test case that fails all the time. I believe that there is more to the
problem than just the rich text edit style but it is consistent, in that
if you turn it off, there is no explosion under these circumstances.

You may find that there is no problem with your applications. We have
one that does not have this problem but it is not nearly as complicated
and does not use as many layers of inheritance.

Randy

[bpo...@gmx.de]

Hi,

we also have the problem that PB 11.5 has random crashes in the
PBSHR115.dll.
Jeff, do you have already an test application sent to Sybase?

Best regards

Benjamin

[bpo...@gmx.de]

Hi,

we have found, that in our nuo_base_ds (our base datastore class) in
the retrieverow event three lines sourcecode has crashed our app.
The instructions were very simple and only used once in the whole
app. . Now we have cleared the retrieverow event and it seems that
erverything works fine.

For the Sybase support team we could reproduce an app. crash
(pbshr115.dll) with PB 11.5 Build 3127 when you often trigger the
dw.retrieve() while the first retrieve still loading data and then
clicking in the dw.
The case number(s) are 11515147 and 11515410. There is a workaround
for that but for our app. very complex.

-------
We have found the root cause, customer call dw retrieve in TabPage 2
SelectionChanged event , while the retrieve is still in progress, he
switched to tabpage 1 and back to tabpage 2 again, which calls dw
retrieve again, leading to reentrance of dw retrieve, which may ruin
the memory, this is not allowed in DW. It's difficult and risky for
us to control this, but PowerBuilder developers have many methods to
handle such situations. So, it's better to leave it to PB developer to
deal with this.

What's your opinion?

Here're 2 samples to use.

1. disable the tabpage while retrieving in SelectionChanged event.

IF newindex > 0 THEN
tab_1.Control[newindex].enabled = false
tab_1.Control[newindex].TriggerEvent ("ue_retrieve")
tab_1.Control[newindex].enabled = true
END IF

2. Use global variables to control whether to call retrieve or not.
------