Deadlock-Problem with SB 7.3.3166

[NewsArchive]

Hi Friedrich,

as a quick information for you: I have a deadlock/hang with SB 7.3.3166
with no changes in my setup since SB 7.2.

This is just a quick note to you. I'll gather more information and keep
you posted.

Markus

[NewsArchive]

Hi Markus,

> as a quick information for you: I have a deadlock/hang with SB 7.3.3166
> with no changes in my setup since SB 7.2.
>
> This is just a quick note to you. I'll gather more information and keep
> you posted.

Is this in the IDE (during the compile) or in your install (at runtime)?

Thanks,
Friedrich

[NewsArchive]

Runtime.

I call a second SB-Installer from my first installer. The second runs
through the whole(?) script but does not terminate. The first installer
waits for the second and so the whole setup hangs.

Markus

[NewsArchive]

> Runtime.
>
> I call a second SB-Installer from my first installer. The second runs
> through the whole(?) script but does not terminate. The first installer
> waits for the second and so the whole setup hangs.

Hmm, nothing changed in #3166. There was a modification in #3162:

---
IMPROVEMENT: Installer: The "Progress Dialog" runs on its own thread to
avoid possible dead-locks when launching external applications
with the "Wait for Program" option enabled.
---

Can you reproduce this with a simple script?

Thanks,
Friedrich

[NewsArchive]

Hi Friedrich,

it is a sporadic problem. I'll force the usage of sbeventlog and then
I'll wait for the next time, the problem occurs.

One time, I've seen, that the first (outer) installer does not terminate
at the end.

So it is eventually not related to the call of the second (inner) setup.

Markus

[NewsArchive]

Hi Markus,

> it is a sporadic problem. I'll force the usage of sbeventlog and then I'll
> wait for the next time, the problem occurs.
>
> One time, I've seen, that the first (outer) installer does not terminate
> at the end.
>
> So it is eventually not related to the call of the second (inner) setup.

Very strange. Before we released SB73, we tested your "OuterSetup.sb7" and
"DBUpdater.sb7" scripts and the "wait" process worked as expected.

So perhaps it's another function that does not "return". Perhaps still the
"register font" function?

Friedrich

[NewsArchive]

Hi Friedrich,

I get not sbevent.log. What am I doing wrong? See attached screen shot.

Markus

[NewsArchive]

Markus,

>
> I get not sbevent.log. What am I doing wrong? See attached screen shot.
>

You cannot specify the path, only the file name!

test.exe /E2 "test.txt"

Friedrich

[NewsArchive]

:-(

Markus Zander

[NewsArchive]

>
> :-(
>

We can add a function to set both the path name and file name if you want.
We added the following in SB73:

---
FEATURE : Installer: Add new /E1 and /E2 event logging mode command line
options to create an unique sbevents_GUID.txt logging file
name (/E1) or set the name of the event logging file
(/E2 "filename").
---

Friedrich