I think having to debug Alex's latest breakage (bugcheck at the end of 2nd stage setup) so I can continue debugging one of his earlier breakages (bug 1263) is asking just a bit too much. I'll go do something non-ReactOS related for the next couple of days.
GvG
But it's more "correct" ;-)
Casper
-----Original Message----- From: ros-dev-bounces@reactos.org [mailto:ros-dev-bounces@reactos.org] On Behalf Of Ge van Geldorp Sent: 12. januar 2006 12:49 To: 'ReactOS Development List' Subject: [ros-dev] Enough is enough
I think having to debug Alex's latest breakage (bugcheck at the end of 2nd stage setup) so I can continue debugging one of his earlier breakages (bug 1263) is asking just a bit too much. I'll go do something non-ReactOS related for the next couple of days.
GvG
Ge van Geldorp wrote:
I think having to debug Alex's latest breakage (bugcheck at the end of 2nd stage setup) so I can continue debugging one of his earlier breakages (bug 1263) is asking just a bit too much. I'll go do something non-ReactOS related for the next couple of days.
GvG
Hi,
Sorry, I do not have access to 10 different configurations. As soon as I was made aware of the breakage I fixed it (go check) and tried VMWare. It worked perfectly. It was 12:20AM so I went to sleep (I am allowed to sleep, right?). Today I woke up (10 minutes ago) and I've been made aware of somethign else that broke, and I'm working on fixing it.
Best regards, Alex Ionescu
Alex Ionescu wrote:
Ge van Geldorp wrote:
I think having to debug Alex's latest breakage (bugcheck at the end of 2nd stage setup) so I can continue debugging one of his earlier breakages (bug 1263) is asking just a bit too much. I'll go do something non-ReactOS related for the next couple of days.
GvG
Hi,
Sorry, I do not have access to 10 different configurations. As soon as I was made aware of the breakage I fixed it (go check) and tried VMWare. It worked perfectly. It was 12:20AM so I went to sleep (I am allowed to sleep, right?). Today I woke up (10 minutes ago) and I've been made aware of somethign else that broke, and I'm working on fixing it.
Best regards, Alex Ionescu __________________________
Next time it's 4AM in Montreal and you feel angry because head is broken and don't realize that I don't test ReactOS in my sleep, please wake me up and page me at 1-514-581-7156. I will wake up and fix head.
Best regards, Alex Ionescu
Ge van Geldorp wrote:
I think having to debug Alex's latest breakage (bugcheck at the end of 2nd stage setup) so I can continue debugging one of his earlier breakages (bug 1263)
Sorry, there is absolutely no proof that I caused 1263, except of course if you take blight's word for it, who has a past history of blaming every single KDBG breakage on me and attributing made up quotes to me. Oh, what's that? I actually FIXED some bugs in KDBG over time according to SVN logs? No no, it couldn't be... SVN must have a bug...
Best regards, Alex Ionescu
From: Ge van Geldorp
I think having to debug Alex's latest breakage (bugcheck at the end of 2nd stage setup) so I can continue debugging one of his earlier breakages (bug 1263) is asking just a bit too much. I'll go do something non-ReactOS related for the next couple of days.
Finished my other project and decided to get back to serious ReactOS development tonight, only to find that this time GDB debugging is seriously broken (breakpoints don't work anymore, I can set them but they are not triggered). Oh well, there's still plenty of stuff on my non-ReactOS todo list.
GvG