[chromium-dev] Re: linux: debugging sandboxed renderers ?
On Tue, Jul 21, 2009 at 4:49 AM, Evan Martin wrote: > On Tue, Jul 21, 2009 at 3:39 AM, Antoine Labour wrote: >> >> On Tue, Jul 21, 2009 at 3:32 AM, Adam Langley wrote: >>> On Tue, Jul 21, 2009 at 3:27 AM, Antoine Labour wrote: What's the best practice for debugging sanbox-related issues ? >>> >>> Usually you can just ask me: the reason you can't create shared memory >>> is because you're trying to use POSIX shared memory, which requires >>> filesystem access. You can use SysV shared memory without issues, but >>> be careful to get the reference counting correct. (See >>> render_process.cc for an example of doing it.) >> >> Those are SysV shared memory - for TransportDIB. Apparently it's not >> the creation that fails (I don't get the DLOG), but some issue >> further, hence why I wanted to debug. >> >>> The other way is to comment out the setting of the DUMPABLE flag in >>> zygote_main_linux.cc and then you'll be able to attach with GDB. >> >> Ah, ok, thanks ! I'll try that. > > Please add notes to > http://code.google.com/p/chromium/wiki/LinuxDebugging once you've > reached a conclusion! > Done. I added instructions that aren't yet valid (until http://codereview.chromium.org/159124 is in). Antoine --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: linux: debugging sandboxed renderers ?
On Tue, Jul 21, 2009 at 3:39 AM, Antoine Labour wrote: > > On Tue, Jul 21, 2009 at 3:32 AM, Adam Langley wrote: >> On Tue, Jul 21, 2009 at 3:27 AM, Antoine Labour wrote: >>> What's the best practice for debugging sanbox-related issues ? >> >> Usually you can just ask me: the reason you can't create shared memory >> is because you're trying to use POSIX shared memory, which requires >> filesystem access. You can use SysV shared memory without issues, but >> be careful to get the reference counting correct. (See >> render_process.cc for an example of doing it.) > > Those are SysV shared memory - for TransportDIB. Apparently it's not > the creation that fails (I don't get the DLOG), but some issue > further, hence why I wanted to debug. > >> The other way is to comment out the setting of the DUMPABLE flag in >> zygote_main_linux.cc and then you'll be able to attach with GDB. > > Ah, ok, thanks ! I'll try that. Please add notes to http://code.google.com/p/chromium/wiki/LinuxDebugging once you've reached a conclusion! --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: linux: debugging sandboxed renderers ?
On Tue, Jul 21, 2009 at 3:32 AM, Adam Langley wrote: > On Tue, Jul 21, 2009 at 3:27 AM, Antoine Labour wrote: >> What's the best practice for debugging sanbox-related issues ? > > Usually you can just ask me: the reason you can't create shared memory > is because you're trying to use POSIX shared memory, which requires > filesystem access. You can use SysV shared memory without issues, but > be careful to get the reference counting correct. (See > render_process.cc for an example of doing it.) Those are SysV shared memory - for TransportDIB. Apparently it's not the creation that fails (I don't get the DLOG), but some issue further, hence why I wanted to debug. > The other way is to comment out the setting of the DUMPABLE flag in > zygote_main_linux.cc and then you'll be able to attach with GDB. Ah, ok, thanks ! I'll try that. Antoine --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: linux: debugging sandboxed renderers ?
On Tue, Jul 21, 2009 at 3:27 AM, Antoine Labour wrote: > What's the best practice for debugging sanbox-related issues ? Usually you can just ask me: the reason you can't create shared memory is because you're trying to use POSIX shared memory, which requires filesystem access. You can use SysV shared memory without issues, but be careful to get the reference counting correct. (See render_process.cc for an example of doing it.) The other way is to comment out the setting of the DUMPABLE flag in zygote_main_linux.cc and then you'll be able to attach with GDB. Cheers AGL --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
