On Mon, 2007-06-18 at 22:41 -0600, Ximsce wrote: > The exception handling doesn't seem to be working, I'm compiling from > subversion at the moment (takes 2 hours on my sadly out-dated computer). > What version would you say is in the repository?
Unfortunately it's not in the repository. I'll create a 0.50 release
today (if all goes well), then commit the exception handling code for
cegcc, then continue developing the same thing for mingw32ce (I've only
got a prototype for it right now, needs to be integrated with the
toolset).
Danny
> Gdb fails saying it can't find .synce/active_connection which I'm
> guessing is because I'm connected to the iPaq through synce-gnome and
> odccm compiled out of their respective repositories (so non-standard)...
>
> I'm perfectly willing to blame the iPaq I'm using for this issue, as it
> was right after it crashed running my application that things stopped
> working. I'm considering resetting to factory defaults, but I'm not
> sure how well that would go over with its owner.
>
> Cheers,
> Matt
>
> Danny Backx wrote:
> > On Sun, 2007-06-17 at 22:14 -0600, Ximsce wrote:
> >> Sorry to keep spamming the list with these newbie questions, but I'm in
> >> a bit of a bind and my deadline approaches.
> >>
> >> I had a program that was working fine, and suddenly a bunch of included
> >> methods have stopped working (causing immediate exit of the program,
> >> without even flushing my log file). Functions that are failing include
> >> execv(), glob(), and strcat(). I read in the documentation that this
> >> could be caused by a conflict between the coredll and cegcc.dll for
> >> stdio functions. Is there a way to force arm-wince-cegcc-gcc to compile
> >> with the cegcc.dll versions of libraries? When I run
> >> arm-wince-cegcc-objdump it appears to be including these functions from
> >> cegcc.dll, but I'm not entirely positive about the output of that tool.
> >
> > Debugging on an embedded system can be such fun :-)
> >
> > Two ideas that may be of help in determining the cause, or the exact
> > statement, of the error.
> >
> > 1. Use gdb (arm-wince-cegcc-gdb). Have it run your application, and see
> > where it traps a signal.
> >
> > 2. If you're using one of my more recent binary distributions then you
> > may have support for trapping exceptions. Undocumented ;-)
> >
> > Use regeditce or so on your PDA to define
> > HKEY_CURRENT_USER -> cegcc -> debug
> > and give it the string value "dialog"
> >
> > If you have one of my recent distributions (and for now only in cegcc)
> > then the application will pop up a dialog describing the problem,
> > instead of just crashing silently.
> >
> > Beware, this is/was experimental code. I believe I have it stable now
> > but the 0.14 or 0.15 may have hickups.
> >
> > Danny
--
Danny Backx ; danny.backx - at - scarlet.be ; http://danny.backx.info
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/
_______________________________________________ Cegcc-devel mailing list Cegcc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cegcc-devel
