- 06 Apr, 2020 26 commits
-
-
Alexandre Julliard authored
Signed-off-by:Alexandre Julliard <julliard@winehq.org>
-
Alexandre Julliard authored
Signed-off-by: -
Alexandre Julliard authored
Signed-off-by: -
Alexandre Julliard authored
Signed-off-by: -
Alexandre Julliard authored
Signed-off-by: -
Zebediah Figura authored
Some application filters enumerate types without a format block. Signed-off-by:
Zebediah Figura <z.figura12@gmail.com> Signed-off-by:
-
Zebediah Figura authored
Signed-off-by:
-
Zebediah Figura authored
Signed-off-by:
-
Zebediah Figura authored
Signed-off-by:
-
Zebediah Figura authored
Signed-off-by:
-
Chip Davis authored
These are aliases for another symbol. They are often seen on Mac OS when a dylib reexports some symbols defined in another dylib. Signed-off-by:
Chip Davis <cdavis@codeweavers.com> Signed-off-by:
-
Chip Davis authored
This makes it easier to copy and paste the command into the shell. Signed-off-by:
-
Zebediah Figura authored
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=45699Signed-off-by:
-
Zebediah Figura authored
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=45699Signed-off-by:
-
Zebediah Figura authored
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=45699Signed-off-by:
-
Zebediah Figura authored
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=45699Signed-off-by:
-
Rémi Bernon authored
No real need for a context member for that as well, the mapping is quite straightforward. It also simplifies handle_exception. Signed-off-by:
Rémi Bernon <rbernon@codeweavers.com> Signed-off-by:
-
Rémi Bernon authored
As in the previous patch, return TRUE if the debug event should be ignored or FALSE is we should tell gdb. There's no need to have an in_trap context member for that. Signed-off-by:
-
Rémi Bernon authored
It was returning a mix of TRUE/FALSE and in some cases DBG_CONTINUE. Let's return TRUE if the exception has been handled and should be ignored, or FALSE if not and if we should notify gdb. Signed-off-by:
-
Rémi Bernon authored
Signed-off-by:
-
Rémi Bernon authored
We read it into a void* so we also need to zero initialize it in case the target pointer size is shorter than ours. Signed-off-by:
-
Zebediah Figura authored
Signed-off-by:
Zebediah Figura <zfigura@codeweavers.com> Signed-off-by:
-
Jeff Smith authored
Signed-off-by:
Jeff Smith <whydoubt@gmail.com> Signed-off-by:
Vincent Povirk <vincent@codeweavers.com> Signed-off-by:
-
Jeff Smith authored
Signed-off-by:
-
Jeff Smith authored
Signed-off-by:
-
Jeff Smith authored
Signed-off-by:
-
- 03 Apr, 2020 14 commits
-
-
Gijs Vermeulen authored
Signed-off-by:
Gijs Vermeulen <gijsvrm@gmail.com> Signed-off-by:
-
Gijs Vermeulen authored
Signed-off-by:
-
Gijs Vermeulen authored
Signed-off-by:
-
Nikolay Sivov authored
Signed-off-by:
Nikolay Sivov <nsivov@codeweavers.com> Signed-off-by:
-
Nikolay Sivov authored
Signed-off-by:
-
Nikolay Sivov authored
Signed-off-by:
-
Nikolay Sivov authored
Signed-off-by:
-
Nikolay Sivov authored
Signed-off-by:
-
Zebediah Figura authored
Signed-off-by:
-
Rémi Bernon authored
Signed-off-by:
-
Rémi Bernon authored
This reports the full register sets to gdb, telling it about custom offsets and sizes. It will make the gdb specific register length not required anymore. We also have to report architecture specific vector types and flags that are normally builtin in gdb as it does not load them anymore when custom register set is reported. This makes gdb stop using its incorrect heuristics and actually request the library list, it now correctly gets PE modules information and is able to correctly use debug info from mixed modules. Signed-off-by:
-
Rémi Bernon authored
Signed-off-by:
-
Rémi Bernon authored
Signed-off-by:
-
Rémi Bernon authored
In order not to repeat the features, registers are expected to be ordered and grouped by feature. If feature name is set only on the first register of a new feature. Signed-off-by:
-
