Hello Sebastien,
I am not sure of the difference between a stacktrace and a backtrace. Here is what I do
In terminal
gdb evolution 2>&1 | tee gdb-evolution.txt handle SIG33 pass nostop noprint set pagination 0 run
Then in the Evolution gui
Create an event that recurs every week. Save the event Edit the event by changing the time. Select all (freezes at this step).
In Terminal ctr c backtrace full info registers thread apply all backtrace quit
Attached is the file.
Cheers, Jeff
Sebastien Bacher wrote: > could you get an evolution-data-server stacktrace using gdb? > >
Hello Sebastien,
I am not sure of the difference between a stacktrace and a backtrace.
Here is what I do
In terminal
gdb evolution 2>&1 | tee gdb-evolution.txt
handle SIG33 pass nostop noprint
set pagination 0
run
Then in the Evolution gui
Create an event that recurs every week.
Save the event
Edit the event by changing the time.
Select all (freezes at this step).
In Terminal
ctr c
backtrace full
info registers
thread apply all backtrace
quit
Attached is the file.
Cheers, Jeff
Sebastien Bacher wrote: data-server stacktrace using gdb?
> could you get an evolution-
>
>