PR# 13650 Trying to Submit Bug, saving trace, then trying to submit bug causes uncaught exception

When I got an internal estudio exception, I clicked on Submit Bug.
I entered my username and password and clicked Login, but it said username and
password were not valid (perhaps things are not setup yet).
So I clicked Cancel, then clicked on Save Trace.
In resulting file dialog, I clicked Cancel.
Then I clicked on Submit Bug again and estudio reported an uncaught exception
   (trace attached).

I believe everything in this report has been resolved.  Closing report.

The original bug reported in this report seems to be fixed in rev 72906
(or maybe I just have a newer version of libcurl, since I'm now using
Solaris 10).  I will leave it to you to decide whether to close this
report, since there are a number of other issues mentioned in this thread.

This problem still happens with rev 71477 (final 6.1 release).
Reopening report.

Note that I also cannot login using a valid username and password on
Solaris SPARC 32-bit (username "prestoat2000", you can find the
password) though I was able to login on Solaris 10 on x86 and
successfully submitted a test bug report on that platform.  We have
an older version of libcurl (not sure what version, but some of the
files are dated from 2004).  Don't know if this might be the cause
of the login failure problem.  I can find out the libcurl version if that
would be helpful.

Hi David,

The bug:

"Undock Standard buttons toolbar and move quickly up and down over tool bar
area (docking and undocking) until estudio crashes (usually within 10 seconds)."

is fixed in revision#71279.

Thanks,
Larry

Is there a bug report for the installer error? If no can you submit one so we can track it?

For future reference, there is no need to uninstall interim releases after installing an initial new interim release, just download the .zip or the .7z archive and extract the contents over you ES installation.

I was using an older version (71123 instead of 71223 - I was fooled by the
very similar version numbers).  I uninstalled 71123 but am unable to install
71223.  I'm getting the same "error 2909" from the installer that I got before.
Last time, removing the whole "ISE" key and subkeys solved the problem but this
time it did not.  So I can't go any further on this on Windows XP at the moment.

I think I might have an older version on Windows XP, without realizing it.
I will check tonight.  Over the weekend, I did definitely reproduce the
same uncaught exception trace originally reported on Solaris on a 
Windows XP machine at my Dad's.  That one was definitely 71223 (released
version).

I'm using EiffelStudio 6.1.7.1179, older than the one you have. It's the released edition. I've attached a screen grab from the exception submit dialog. I've done this because it reads like we are not using the same UI. It appears that you are using the old submit dialog, which I can confirm via the latest stack trace using EB_EXCEPTION_SUBMIT_DIALOG instead of the new ES_EXCEPTION_SUBMIT_DIALOG (new ES_ prefix over the old EB_). This is not consistent with your initial report with the trace stack113.txt attached, which used the correct ES_EXCEPTION_SUBMIT_DIALOG.

I guess there is version mismatch between your WinXP and Solaris installations.

OK, got 6.1.71223 installed on Windows XP at home.
To reproduce problem:

Start estudio.  Click Cancel.
Undock Standard buttons toolbar and move quickly up and down over tool bar area (docking and
   undocking) until estudio crashes (usually within 10 seconds).
Click on Submit Bug.
Enter username "aaaaaa" and password "aaaaaa".  Click Submit.
When estudio reports error 23, click OK.
Click on Submit Bug again.
Enter username "aaaaaa" and password "aaaaaa".  Click Submit.
Estudio reports uncaught exception with trace (seems to be a slightly different
trace than the one I got previously):

-------------------------------------------------------------------------------
Class / Object      Routine                Nature of exception           Effect
-------------------------------------------------------------------------------
STRING_8            infix "+" @1                                        
<0000000005953770>                         Feature call on void target.  Fail
--------------------
....
Output truncated, Click download to get the full message

I can't reproduce anything here at work, since we don't have libcurl
installed here yet.  In my tests, any internal exception was sufficient
to reproduce the problem.  You could try the error reported in bug
12296 (add watch expression `agent do end' in debugger and then
freeze system).  Another possibility is to quickly undocked one of
the tool bars, which often causes a crash in rev 71223 (fixed in
a later revision).

Incidentally, I can't try Windows XP at home because I cannot install 6.1.
I uninstalled Eiffel 6.0 and then tried to install 6.1.  I got a
failure trying to unregister some component (error 2909). I suspect I have to
clean up something in the registry but don't know what or how.

David, I took a look at the code and tested EiffelStudio on WinXP. I'm having trouble reproducing the problem. It might be the type of exception being thrown. Can you provide a repo as to how you produce the original exception in EiffelStudio?

I have now also reproduced this problem on Windows XP.
To reproduce:  After getting an Internal EiffelStudio Exception,
click on the Submit Bug button.  Enter username "aaaaaa" and
password "aaaaaa" (presumably invalid) and click Login button.
When estudio reports failure to login, click OK, then click Cancel.
Click on Submit Bug button again.  Estudio reports an uncaught
exception (call on Void target in {ES_EXCEPTION_SUBMIT_DIALOG}.synopsis).
Full trace previously attached.

Actually, for me it happens on Solaris x86 32-bit under JDS (rev 71239).
I just reproduced it in this environment.  I used Sun Studio 12 to compile
with automatic build scripts.

I can reproduce this problem now. This is another problem that ONLY happens on CDE . On JDS it works fine.

We are analyzing it now.

Still happens for me in rev 71239.  Reopening report.

We have new exception dialog which works now as described in bug#13630.

I have tried to reproduce this problem in the way you mentioned. It works fine in revision#71238 on Solaris 32bits.

Thanks for your report.

Attachments for problem report #13650