Miguel: It sounds like you're saying that if you build cvs with HB_NO_PROFILER (the default), and then try to call any of the profiler functions, you get a gpf.
If so, this isn't OK to ship. We've always supported transparent calls (no error, just no results) to the profiler funcs when its pieces are not linked in, and now users would get a gpf instead of whatever happened before. We would need to fix it to either throw a linker error because the functions themselves are not linked in (this isn't compatible with prior behavior but at least generates a useful error), or make sure that the current gpf is fixed. -- Brian Hays > -----Original Message----- > From: Miguel Angel Marchuet [mailto:miguelan...@marchuet.net] > Sent: Friday, January 16, 2009 10:12 AM > To: Luis Krause Mantilla; xharbour developer list > Subject: Re: [xHarbour-developers] More on the profiler issues > > Luis Krause Mantilla escribió: > > Even compiling source\rtl\profiler with -D__TEST__ gpf's as well. > > > > Any ideas where the problem lies? > > > > to compile xharbour with profiler wout need compile it with macro > > HB_USE_PROFILER > > it was implemented few days ago. > > in other case setup automatically add HB_NO_PROFILER and then profiler > generate GPF > > Best regards, > Miguel Angel Marchuet ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ xHarbour-developers mailing list xHarbour-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xharbour-developers
