The problem though, unless I'm missing something, is in a thread, with an
unhandled crash the code checks isCrashBound,
(CodenameOneThread#handleException) which would be false and so would never
call the newly installed logger (Log.e())
public static void handleException(Throwable err) {
See this post, which includes a snippet that extracts stack traces using a
temporary logfile.
You can adapt this to capture all the log events - but except for stack
traces I think you're
better off using a private mechanism to log info.
https://groups.google.com/forum/#!searchin/codenameone-di
You can file an RFE for that although I'm not sure when we'll get around to
it. 3.6 is already overbooked and 3.7 is filling up quickly with tasks.
--
You received this message because you are subscribed to the Google Groups
"CodenameOne Discussions" group.
To unsubscribe from this group and st
ok, so I have a situation that requires some flexibility. The tablets are
air gapped so using the "cloud based crash reporting" wont work. We can
use email based reporting (they can save the logfile as a draft and then
send when they are connected)
However the sendlog function is static (not
I use this code to capture the contents of a log file. Its a bit obscure
because it threads
a needle through the standard codename1 class "Log" to create a temporary
log file.
class LogCapture extends Log
{Log oldLog;
StringWriter myWriter;
LogCapture()
{ oldLog = Log.getInsta
Log.e() prints the stack trace etc. Grabbing system out/err is a bit of a
technical challenge across platforms.
--
You received this message because you are subscribed to the Google Groups
"CodenameOne Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an
I am interested in getting the stacktrace. In my desktop java apps I
redirect System.out and Sytem.err uploading to a website I already
have, but others might be intersted in that.
Peter
On 10/07/2016 09:02 PM, Dave Dyer wrote:
assuming you have a web site to receive it, some simple perl ca
assuming you have a web site to receive it, some simple perl can suck in
whatever is posted to it
and store it to a permanent log. I use this for debugging and catching
the unexpected from deployed
applications.
The biggest trick is getting a stack trace (which is also a "pro" feature
for n
Not much beyong the javadocs as far as I recall. Our official way for
reading is the sendLog() method which we use a lot but it's a pro feature.
Writing is just Log.p(),Log.e() where you can just write whatever you want
into the log. I don't have experience in reading the log other than sendLog
