[WinAVR-users] [ winavr-Bugs-1950426 ] Bluescreen after compilation of Interrupts with wrong header

[SourceForge.net <no...@so...>]

Bugs item #1950426, was opened at 2008-04-24 09:50
Message generated for change (Comment added) made by andre11
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=520074&aid=1950426&group_id=68108

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: AVR-LibC
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Andre (andre11)
Assigned to: Nobody/Anonymous (nobody)
Summary: Bluescreen after compilation of Interrupts with wrong header

Initial Comment:
Hi there,

I'm working under Vista64 with AVRStudio 4.14 and WINAVR 20080411.

I have a Project where I use the USART recive Interrupt. The accourding code looks like this:

=======
ISR(USART0_RX_vect){

  // some code here

}
=======

When I put the following line in the according header file my System brings up a blue screen when I want to compile the whole thing

=======
ISR(USART0_RX_vect);
=======

I know that I do not need to put this line in the header file instead if including the interrupts.h , but nevertheless I was wondering that Vista can crash with a bluescreen because of this.

The message in the bluescreen says "Bad Pool Caler"

I hope I put in all information you need.

----------------------------------------------------------------------

>Comment By: Andre (andre11)
Date: 2008-04-30 09:06

Message:
Logged In: YES 
user_id=2071293
Originator: YES

I'm pretty sure it's no hardware Probleme since it's a brand-new machine.
I'm going to try this on a other machine later on.

----------------------------------------------------------------------

Comment By: Preston Wilson (rpwilsonjr)
Date: 2008-04-24 16:23

Message:
Logged In: YES 
user_id=2066199
Originator: NO

Bug Checks are caused by bugs in device drivers, bugs in the Window's
kernel, and bad hardware.  User level programs can trigger such bugs, but
the user level program itself is not the problem.

If all you are doing is compiling with gcc and encounter Bug Check
BAD_POOL_CALLER, then it is highly probable that you have a hardware
problem, and it is most likely bad RAM.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=520074&aid=1950426&group_id=68108