Hi,
On Thu, Dec 21, 2017 at 02:11:22PM -0700, zulu4711 wrote:
>
> The thread that is started that takes the SIO data and feeds them to
> pppos_input() was something I did as I understood from Simon that if
> PPP_INPROC_IRQ_SAFE is 1, that was safe to do.
>
> Can you explain to me if these assu
Any comments on this ?
It seems to work fine, have had it running on a testsystem for a week or
more..
--
Sent from: http://lwip.100.n7.nabble.com/lwip-users-f3.html
___
lwip-users mailing list
lwip-users@nongnu.org
https://lists.nongnu.org/mailman/l
Thanks for input!
I'm sorry, but I need to take a couple of steps back now (english is not my
native language...)
First of all the initialization sequence.
In my main() I changed now to:
dial the modem
starts a thread that will eventually feed serial data to
pppos_input() once eve
goldsimon wrote:
> Core locking is really for the you layer only.
That should have been API layer!
Simon
___
lwip-users mailing list
lwip-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lwip-users
Sylvain Rochet wrote:
> [..]
>Looks like you are calling netif_* functions outside the lwIP core
>thread, guess what ? This is not thread safe. (Or maybe it is with core
>locking enabled).
No, it's not. Core locking is really for the you layer only.
Simon
_
Hi zulu4711,
On Thu, Dec 21, 2017 at 10:57:55AM -0700, zulu4711 wrote:
> Thanks for input Sylvain!
>
> I'm sure that I'm doing something wrong, I just need to find out what ;)
> In the project this will eventually go into, I have around 300.000 lines of
> C code and more than 50 separate threads
Thanks for input Sylvain!
I'm sure that I'm doing something wrong, I just need to find out what ;)
In the project this will eventually go into, I have around 300.000 lines of
C code and more than 50 separate threads running so a "non RTOS" operation
is not possible.
I was led to believe (not payi
Hi zulu4711,
On Thu, Dec 21, 2017 at 03:06:14AM -0700, zulu4711 wrote:
>
> Yes, it seems like a threading violation like I had before and this is
> surely because of me not having a full insight to what is legal to call and
> what is not legal to call in the stack when running in threaded mode.
Thanks for input Simon!
Yes, it seems like a threading violation like I had before and this is
surely because of me not having a full insight to what is legal to call and
what is not legal to call in the stack when running in threaded mode.
I checked, and I called ppp_close() from another thread t
zulu4711 wrote:
> [..]
> The crash happens always when the line is dropped and PPP reports
> PPP_PHASE_ESTABLISH (6) or thereabouts. I get a protection violation in the
> socket send function (I have a feeling that the send function is in the
> middle "of its thing" when the connection is ripped aw
I should also add that it is not the same place the crash occurs, I have seen
it other places (but did not get a snapshot of where it was but it was also
while the line was dropped and when the socket send function was active)
Any ideas ?
--
Sent from: http://lwip.100.n7.nabble.com/lwip-users-f
and lwipopts.h
/*
* Copyright (c) 2001-2003 Swedish Institute of Computer Science.
* All rights reserved.
*
* Redistribution and use in source and binary forms, with or without
modification,
* are permitted provided that the following conditions are met:
*
* 1. Redistributions of source
Code from the application:
//---
//
//---
#define __MODULE__ "Application.c"
int insnumber=0;
#define PPP_USERNAME "Admin"
#d
13 matches
Mail list logo