Re: Tracking down reasons for segvaulting applications
On Monday 28 December 2009, Ivo van den Maagdenberg wrote: > 2009/12/28 Patrick Beck : > > The downside of this all is that I will have to have a GPS fix, which > will force me to go outside in wintertime :/ Being near a window is usually good enough, although getting the fix may take a bit longer than it would outside. There are a few exotic window coatings that can interfere with the signal though. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Tracking down reasons for segvaulting applications
On Mon, 2009-12-28 at 23:43 +0100, Ivo van den Maagdenberg wrote: > 2009/12/28 Patrick Beck : > > Hi, > > > > is that not a normal enlightenment (window manager) error message? I > > think it will be useful to start the script from the command line. Then > > you get the error output directly from the python interpreter. > > > > Ok, all irony aside, I will start with a test session from the command > line and see what I can find. Then after that I'll throw some strace > at it. > > The downside of this all is that I will have to have a GPS fix, which > will force me to go outside in wintertime :/ > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community Lucky you - its summer here - 36c on the way to 39c today. I dont want to go outside either :) BillK ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Tracking down reasons for segvaulting applications
On Mon, 28 Dec 2009 23:43:12 +0100 Ivo van den Maagdenberg said: > 2009/12/28 Patrick Beck : > > Hi, > > > > is that not a normal enlightenment (window manager) error message? I > > think it will be useful to start the script from the command line. Then > > you get the error output directly from the python interpreter. > > enlightenment pops up these dialogs whenever a child it is tracking (that it would have exec'ed) exitsabnormally. either non-zero exit codes (this is meant to imply an error at the higher levels of the app - missing file, missing config, etc. etc. but the app exits with a non-zero exit code) or exits where it died due to a signal (segfault, abort etc.) e also nicely is capturing stdout and stderr and will provide that for you if it has any so maybe the app went "help! no config!" on stderr and then exit(-1)'ed). this is what you get as opposed to the window mysteriously vanishing and you process having vanished and you have no idea why. > Ok, all irony aside, I will start with a test session from the command > line and see what I can find. Then after that I'll throw some strace > at it. > > The downside of this all is that I will have to have a GPS fix, which > will force me to go outside in wintertime :/ you don't need a whole session from the cmd-line, just tun your app from it under gdb (yes it is installable on the device if your oe repositories are complete enough - or you use debian). i.e. just ssh in, then export DISPLAY=:0 to work on the local display and run app and debug as u would anywhere on linux on a desktop. (sshing in just gets you a sane kbd and desktop screen to use as your debug console :)) -- - Codito, ergo sum - "I code, therefore I am" -- The Rasterman (Carsten Haitzler)ras...@rasterman.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Tracking down reasons for segvaulting applications
2009/12/28 Patrick Beck : > Hi, > > is that not a normal enlightenment (window manager) error message? I > think it will be useful to start the script from the command line. Then > you get the error output directly from the python interpreter. > Ok, all irony aside, I will start with a test session from the command line and see what I can find. Then after that I'll throw some strace at it. The downside of this all is that I will have to have a GPS fix, which will force me to go outside in wintertime :/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Tracking down reasons for segvaulting applications
Hi, is that not a normal enlightenment (window manager) error message? I think it will be useful to start the script from the command line. Then you get the error output directly from the python interpreter. with kind regards Patrick Beck Am Montag, den 28.12.2009, 20:39 +0100 schrieb Ivo van den Maagdenberg: > My python app ends regularly with a segmentation fault and offers to > save a log by means of a gtk dialog. The actual log contains very > little helpful info. I'd like to know how to catch more fish. > > " > Error Signal Information: > /usr/bin/xyz was interrupted by a Segmentation Fault. > > Output Data: > There was no output > > Error Logs: > There was no error message > " > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community > signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Tracking down reasons for segvaulting applications
2009/12/28 Ivo van den Maagdenberg : > 2009/12/28 hab keen oh ne : >> How do I develop software? >> Could you please not ask stupid much too frequently asked questions? >> strace your program? >> debug it? >> > Thanks for you friendly reply. > Ah no, it's a 4-point multiple-choice anwser! I guess strace is my friend... troll posts are riddle sometimes =) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Tracking down reasons for segvaulting applications
sounds like a bug in nthe underlying python library. i'd try to track down the line of my code where it happens and check google for any reports regarding the python code called. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Tracking down reasons for segvaulting applications
Am Montag, den 28.12.2009, 21:29 +0100 schrieb Ivo van den Maagdenberg: > 2009/12/28 hab keen oh ne : > > How do I develop software? > > Could you please not ask stupid much too frequently asked questions? > > strace your program? > > debug it? > > > Thanks for you friendly reply. >From that "realname" I wouldn't expect much more. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Tracking down reasons for segvaulting applications
2009/12/28 hab keen oh ne : > How do I develop software? > Could you please not ask stupid much too frequently asked questions? > strace your program? > debug it? > Thanks for you friendly reply. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
AW: Tracking down reasons for segvaulting applications
How do I develop software? Could you please not ask stupid much too frequently asked questions? strace your program? debug it? Von: Ivo van den Maagdenberg An: List for Openmoko community discussion Gesendet: Montag, den 28. Dezember 2009, 20:39:47 Uhr Betreff: Tracking down reasons for segvaulting applications My python app ends regularly with a segmentation fault and offers to save a log by means of a gtk dialog. The actual log contains very little helpful info. I'd like to know how to catch more fish. " Error Signal Information: /usr/bin/xyz was interrupted by a Segmentation Fault. Output Data: There was no output Error Logs: There was no error message " ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community __ Do You Yahoo!? Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. http://mail.yahoo.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Tracking down reasons for segvaulting applications
My python app ends regularly with a segmentation fault and offers to save a log by means of a gtk dialog. The actual log contains very little helpful info. I'd like to know how to catch more fish. " Error Signal Information: /usr/bin/xyz was interrupted by a Segmentation Fault. Output Data: There was no output Error Logs: There was no error message " ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community