search for: incapsulated

On 06/23/2010 10:24, Reid Kleckner wrote: > You said this is on 32-bit x86? My understanding is that in that > case, gdb will use ebp/esp to unwind the stack and doesn't need dwarf. > It may have different behavior on FreeBSD if frame pointers are > normally omitted on that platform. gdb ignores them on Linux x86_64 > because they are generally omitted. > > This might

Please help to work out solution for the following task : There are several users of my application and I want to allow each one to have personal sqlite database. It''s going to be very useful for me when all user''s data incapsulated in one single file. All users can be logged-in at one time. Is it possible to implement it with ruby on rails? If so what is the best way to implement it? May be there were similar tasks requiring different ActiveRecord behavior based on user session data? -- Posted via http://www.ruby-forum....

You said this is on 32-bit x86? My understanding is that in that case, gdb will use ebp/esp to unwind the stack and doesn't need dwarf. It may have different behavior on FreeBSD if frame pointers are normally omitted on that platform. gdb ignores them on Linux x86_64 because they are generally omitted. This might actually be the best explanation for your symptoms, since this is what a gdb

I have this situation when the same code SEGVs in JIT with option -disable-fp-elim and works fine without it. How can this possibly happen? Is it possible that there is a bug in JIT that stack isn't properly lowered for local variables when prologs are present? Or maybe JIT can accidentally use ebp for some values when it's supposed to be only used by frame pointer value. Stack (see