It can be broken
James Miller
Great, just got my first Delphi 2007 catastrophic failure.
Oh well.
P.S. What was I doing? - Just editing a collection on the Structure
window. No, I am not going to put it in QC; chances that sysops
can reproduce this blow up are very slim.
Liz
> P.S. What was I doing? - Just editing a collection on the Structure
> window. No, I am not going to put it in QC; chances that sysops
> can reproduce this blow up are very slim.
How will you know if you dont let them even try?
--
Liz the Brit
Delphi things I have released: http://www.xcalibur.co.uk/DelphiThings
David M
Not going to give them a chance. Poor sport !
Cheers
D
David Moorhouse
Moorhouse Works ltd
www.moorhouse.co.nz
JED
> Great, just got my first Delphi 2007 catastrophic failure.
Not even a callstack for the error?
--
TJSDialog - TaskDialog for other operating systems:
http://www.jed-software.com/jsd.htm
Visual Forms IDE Add In: http://www.jed-software.com/vf.htm
![Dave Nottage [TeamB]'s profile photo](http://lh3.googleusercontent.com/a-/ALV-UjUj2H7buWqfQEwUbLrKsoA_PHkoBpwlol4dHQP1Bjdlf-D3Qto=s40-c)
Dave Nottage [TeamB]
> Just editing a collection on the Structure
> window.
What was the collection?
--
Dave Nottage [TeamB]
Fernando Madruga
an Automated Incident Report. I didn't discover that until after a few
such windows and my curiosity took the best of me to expand that dialog! :)
Tom Corey
Let's see, zero posting history, vague claim, refusal to substantiate.
Yeah. All kinds of impressed.
Mark Reichert
news:xn0f4lbab...@newsgroups.borland.com...
I think he's TObject.
Fernando Madruga
According to another post, he may be the same as TObject, so that's not
zero posting history if that's the case...
Tom Corey
> According to another post, he may be the same as TObject, so that's
> not zero posting history if that's the case...
I see that now. Not exactly a huge credibility booster :)
James Miller
"Liz" <liz_want...@xcalibur.nospam.co.uk> wrote in message news:xn0f4lax...@newsgroups.borland.com...
> > P.S. What was I doing? - Just editing a collection on the Structure
> > window. No, I am not going to put it in QC; chances that sysops
> > can reproduce this blow up are very slim.
> How will you know if you dont let them even try?
Because even I have problems reproducing it.
It's not a simple act of editing the collection,
it is some kind of complex issue that is hard to track down.
James Miller
"Fernando Madruga" <Fernando...@POBox.com> wrote in message news:461510c4$1...@newsgroups.borland.com...
> According to another post, he may be the same as TObject, so that's not
> zero posting history if that's the case...
I don't know who you are talking about. But I hear that TObject is awesome.
:-)
Fernando Madruga
serves no useful purpose! :)
James Miller
"Dave Nottage [TeamB]" <dav...@radsoft.com.au> wrote in message news:4614b65e$1...@newsgroups.borland.com...
> > Just editing a collection on the Structure
> > window.
> What was the collection?
It was a custom descendant from TCollection used as a property
of a component. The collection could be operated fine through
its custom property editor; but as soon as I tried to edit the collection
using the Structure window, the Delphi blew up.
Freddy
credibility :)
That was fast!!!
;) - freddy
"James Miller" <noe...@nospam.invalid> wrote in message
news:46153500$1...@newsgroups.borland.com...
Fernando Madruga
> Haha and you have proven the point that a "real" name doesnt mean
> credibility :)
> That was fast!!!
If we go that route, can you prove that your friends are whom they say
they are? Unless you've known them from early childhood (and even then
with some restrictions!), you can not truly say they are who they say
they are. However, it's easier to refer to them by the name they use
rather than to refer to them as some nos...@nowhere.com... Even if it's
a fake name, it makes dialog much easier! :)
Craig Stuntz [TeamB]
> I don't know who you are talking about.
The guy who posts from the same IP address with the same newsreader
who also asks questions about custom subclasses of TCollectionItem.
You know, that guy.... :)
--
Craig Stuntz [TeamB] · Vertex Systems Corp. · Columbus, OH
Delphi/InterBase Weblog : http://blogs.teamb.com/craigstuntz
Borland newsgroup denizen Sergio González has a new CD of
Irish music out, and it's good: http://tinyurl.com/7hgfr
Mark Reichert
in message news:4615...@newsgroups.borland.com...
> James Miller wrote:
>
>> I don't know who you are talking about.
>
> The guy who posts from the same IP address with the same newsreader
> who also asks questions about custom subclasses of TCollectionItem.
And posted this recently
http://groups.google.com/group/borland.public.delphi.non-technical/msg/db8f502b83846fae?hl=en&
In the Wake Up thread.
Liz
> Because even I have problems reproducing it.
>
> It's not a simple act of editing the collection,
> it is some kind of complex issue that is hard to track down.
Sometimes it takes a few people to club together to actually nail the
exact circumstances, you should always feel you can put things in QC
Andre Kaufmann
> James Miller wrote:
>
>
>> Because even I have problems reproducing it.
>>
>> It's not a simple act of editing the collection,
>> it is some kind of complex issue that is hard to track down.
>
> Sometimes it takes a few people to club together to actually nail the
> exact circumstances, you should always feel you can put things in QC
Sometimes it needs only a single crash dump to track down the problem.
Doesn't D2007 already write one ?
Andre
James Miller
"JED" <nos...@nospam.com> wrote in message news:xn0f4lpcn...@newsgroups.borland.com...
> Not even a callstack for the error?
Will this help?
Faulting application bds.exe, version 11.0.2627.5503, faulting module kernel32.dll, version 5.2.3790.2756, fault address 0x00015e02.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 62 64 73 ure bds
0018: 2e 65 78 65 20 31 31 2e .exe 11.
0020: 30 2e 32 36 32 37 2e 35 0.2627.5
0028: 35 30 33 20 69 6e 20 6b 503 in k
0030: 65 72 6e 65 6c 33 32 2e ernel32.
0038: 64 6c 6c 20 35 2e 32 2e dll 5.2.
0040: 33 37 39 30 2e 32 37 35 3790.275
0048: 36 20 61 74 20 6f 66 66 6 at off
0050: 73 65 74 20 30 30 30 31 set 0001
0058: 35 65 30 32 5e02
James Miller
Application popup: bds.exe - Application Error : The exception unknown software exception (0x0eedfade) occurred in the application
at location 0x77e55e02.
Dave Nottage [TeamB]
> It was a custom descendant from TCollection used as a property
> of a component. The collection could be operated fine through
> its custom property editor; but as soon as I tried to edit the
> collection using the Structure window, the Delphi blew up.
Knowing which component/collection might help.
--
Dave Nottage [TeamB]
Liz
> Sometimes it needs only a single crash dump to track down the
> problem. Doesn't D2007 already write one ?
Same as 2006, I think long as you click details the dumps there..
James Miller
Oops. I did it again. This time I saved the callstack. Here it is:
[20DB8532]{designide100.bpl} StructureViewAPI.TStructureMenuItem.Click + $5E
[2000A455]{rtl100.bpl } System.@CheckAutoResult + $11
[20DB8532]{designide100.bpl} StructureViewAPI.TStructureMenuItem.Click + $5E
[20134C87]{vcl100.bpl } Menus.TMenu.DispatchCommand + $13
[20135DE6]{vcl100.bpl } Menus.TPopupList.WndProc + $82
[20135D35]{vcl100.bpl } Menus.TPopupList.MainWndProc + $1D
[20040DE4]{rtl100.bpl } Classes.StdWndProc + $14
[20160EF8]{vcl100.bpl } Forms.TApplication.ProcessMessage + $FC
[20160F32]{vcl100.bpl } Forms.TApplication.HandleMessage + $A
[20161188]{vcl100.bpl } Forms.TApplication.Run + $CC
[00422971]{bds.exe } bds.bds (Line 196, "" + 7) + $2
If I find a way to reproduce this reliably, I will see if I can put somebody on it to make a QC report.
Chris Burrows
>
> Application popup: bds.exe - Application Error : The exception unknown
> software exception (0x0eedfade) occurred in the application at location
> 0x77e55e02.
This exception code is defined and referenced in
..\Source\RTL\Sys\System.Pas:
cDelphiException = $0EEDFADE;
...
cDelphiException { our magic exception code }
An explanation given in a earlier posting in the b.p.d.language.objectpascal
newsgroup (24 Apr
2000) by Steve Schafer (Team B) is:
<quote>
That particular exception is simply Delphi's own internal code for
identifying a Delphi exception. The fact that it escapes to the
outside indicates that something is wrong with Delphi's
exception-handling mechanism. There are three common scenarios:
1) The exception occurs before the exception-handling mechanism is in
place (e.g., in the initialization section of a unit)
2) The exception occurs after the exception-handling mechanism has
been shut down (e.g., in the finalization section of a unit)
3) The exception-handling mechanism has been corrupted in some way, or
was never there to begin with (which would be the case if the SysUtils
unit were not included in the EXE)
You can also get that exception code if an exception is raised inside
a DLL and not caught within the DLL code.
</unquote>
Chris Burrows
CFB Software
http://www.cfbsoftware.com/gpcp
James Miller
Perhaps we'll narrow this one down, after all.
Bruce McGee
> Oops. I did it again. This time I saved the callstack. Here it is:
Did you click "details" and send an automated incident report to
CodeGear?
--
Regards,
Bruce McGee
Glooscap Software