RE: [ros-dev] More RBuild issues...

[Casper Hornstrup]

>   -----Original Message-----
>  From: ros-dev-bounces(a)reactos.com [mailto:[e-mail]] On Behalf Of Ge
> van Geldorp
>  Sent: 29. maj 2005 21:55
>  To: 'ReactOS Development List'
>  Subject: RE: [ros-dev] More RBuild issues...
>  
> >   From: Casper Hornstrup
> >
> >  The rsym section can be NOLOAD so there is no memory bloat. 
>  
>  It's already NOLOAD... What I do see as a potential problem is that the
>  symbols are loaded into non-paged pool. This is because they're needed
>  during a bug check, at which time we can't page them back in (or read them
>  from the image file).
>  
>  How about introducing a boot option /LOADSYMBOLS, defaulting to YES for DBG
>  := 1 and NO for DBG := 0? That way, a user having a reproducible problem can
>  be instructed to add that option so we can have a good stack trace. Maybe
>  reporterror can load the symbols when needed? Just tossing around some ideas
>  here.
>  
>  Ge van Geldorp. 
I am planning on making reporterror translating the addresses to symbols on
the next boot after a crash in kernel-mode. This mean the symbols only need
to be in memory during the period reporterror is translating a stack trace
and only symbols for modules which are listed in the stack trace are needed
to be loaded.

Symbols in BSOD screens are nice and all, but if you have network capability,
reporterror would be much easier to use since you don't need to write down the
stack trace on paper or grab a camera to report the information to a developer.

Casper