#
515d86da |
|
17-May-2019 |
Adrien Destugues <pulkomandy@pulkomandy.tk> |
debug_server: build a new debug window Use radio buttons laid out vertically so that locales with long labels (no short word for "write core file") can still look nice. This is open for experiment, buttons laid out vertically are another option. At least now we have a window t work from, as BAlert doesn't cut it here. While I'm at it, use a ladybug icon for this one, so it's visibly different from normal application alerts. Change-Id: I08ba9573f132901484224e107404348e7dca97f4 Reviewed-on: https://review.haiku-os.org/c/1459 Reviewed-by: waddlesplash <waddlesplash@gmail.com>
|
#
8028ede7 |
|
15-Jan-2016 |
Rene Gollent <rene@gollent.com> |
Build: Add architecture rule for libshared.a. - As suggested by Ingo, add libshared.a to the architecture name map. This allows it to be linked by its short name like other frequently used libraries. - Adjust all Jamfiles referencing the lib accordingly.
|
#
220d0402 |
|
31-Jul-2014 |
Oliver Tappe <zooey@hirschkaefer.de> |
Use libstdc++, libsupc++ and libgcc from gcc_syslibs. * Instead of faking libstdc++.so from libstdc++.a, use libstdc++.so from the gcc_syslibs build feature for everything except x86_gcc2. * Use libgcc_s.so from the gcc_syslibs build feature for everything but x86_gcc2 (which still carries libgcc as part of libroot.so). * Drop filtering of libgcc objects for libroot, as that is no longer necessary since we're only using libgcc-as-single-object for libroot with x86_gcc2, where the filtered object file doesn't exist. Should the objects that used to be filtered cause any problems as part of libgcc_s.so, we can always filter them as part of the gcc build. * Use libsupc++.so from the gcc_syslibs build feature for everything but x86_gcc2. * Adjust all Jamfiles accordingly. * Deactivate building of faked libstdc++.so for non-x86-gcc2. For x86_gcc2, we still build libstdc++.so from the sources in the Haiku source tree as part of the Haiku build . * Put gcc_syslibs package onto the image, when needed.
|
#
1b744548 |
|
15-Dec-2013 |
Rene Gollent <rene@gollent.com> |
debug_server: Add default action support. - debug_server now supports user configuration of both the general default action to be taken on crashes, and per-app overrides. These are stored config/settings/system/debug_server/settings. In the absence of the file, behavior defaults to prompting the user for an action as before. The file takes on a driver_settings style format as follows: --- default_action user executable_actions { app1 log /path/app2* debug } --- Valid values for an action are: - user = prompt user for action. - kill = silently terminate the crashing team. - debug = attach the debugger to the crashing team. in the debugger. - log / report = save a crash report and terminate the team. If no default_action is specified, "user" is assumed. The executable_actions subsection contains individual overrides of the default. These take the form above, where the individual lines can be only a team name, or a path, with wildcards. Implements first part of #10301.
|
#
b0944c78 |
|
01-Aug-2013 |
Ingo Weinhold <ingo_weinhold@gmx.de> |
More work towards hybrid support * All packaging architecture dependent variables do now have a respective suffix and are set up for each configured packaging architecture, save for the kernel and boot loader variables, which are still only set up for the primary architecture. For convenience TARGET_PACKAGING_ARCH, TARGET_ARCH, TARGET_LIBSUPC++, and TARGET_LIBSTDC++ are set to the respective values for the primary packaging architecture by default. * Introduce a set of MultiArch* rules to help with building targets for multiple packaging architectures. Generally the respective targets are (additionally) gristed with the packaging architecture. For libraries the additional grist is usually omitted for the primary architecture (e.g. libroot.so and <x86>libroot.so for x86_gcc2/x86 hybrid), so that Jamfiles for targets built only for the primary architecture don't need to be changed. * Add multi-arch build support for all targets needed for the stage 1 cross devel package as well as for libbe (untested).
|
#
8215661b |
|
29-Oct-2011 |
François Revol <revol@free.fr> |
Apply patch by 'mt' from ticket #7622 to localize the debug_server alert. Thanks! git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@42979 a95241bf-73f2-0310-859d-f6bbb57e9c96
|
#
338b8dc3 |
|
29-Oct-2005 |
Ingo Weinhold <ingo_weinhold@gmx.de> |
Merged changes from branch build_system_redesign at revision 14573. git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@14574 a95241bf-73f2-0310-859d-f6bbb57e9c96
|
#
c9ce15c9 |
|
14-Jul-2005 |
Ingo Weinhold <ingo_weinhold@gmx.de> |
* Reworked the design: It certainly doesn't make sense to display more than one alert, when two threads of a team crash. Now we have a per team queue of debug messages and a thread per team that processes them (that is usually only the first one). The application class does nothing anymore. * Implemented debugger handover: - In case of normal apps, when the relevant servers needed for GUI are running, we show an alert and, if requested, start a MiniTerminal with gdb for the crashed team. I couldn't really test it, since alerts don't seem to work, respectively crash the app server (usually both ;-). - In case the app server crashes, we always start a consoled with gdb. This does indeed seem to work. A gdb attached to a team is not really useful yet, since the shared object relocations seem to be incorrect, so "bt" is not giving any useful info. git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@13684 a95241bf-73f2-0310-859d-f6bbb57e9c96
|
#
362e09b1 |
|
20-Mar-2005 |
Ingo Weinhold <ingo_weinhold@gmx.de> |
In case of a debugger() call now also prints the debug message. Makes use of the new libdebug.so. git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@11926 a95241bf-73f2-0310-859d-f6bbb57e9c96
|
#
35e49f25 |
|
25-Feb-2005 |
Ingo Weinhold <ingo_weinhold@gmx.de> |
Initial version of our debug server. This is the guy that hangs around waiting for teams to crash to show our favorite alert. Due to the missing app_server we don't show a alert yet. We just print something to /dev/dprintf and kill the team. Unlike R5's debug server ours will probably not provide any debugging functionality itself, but rather employ gdb directly. git-svn-id: file:///srv/svn/repos/haiku/trunk/current@11492 a95241bf-73f2-0310-859d-f6bbb57e9c96
|
#
220d04022750f40f8bac8f01fa551211e28d04f2 |
|
31-Jul-2014 |
Oliver Tappe <zooey@hirschkaefer.de> |
Use libstdc++, libsupc++ and libgcc from gcc_syslibs. * Instead of faking libstdc++.so from libstdc++.a, use libstdc++.so from the gcc_syslibs build feature for everything except x86_gcc2. * Use libgcc_s.so from the gcc_syslibs build feature for everything but x86_gcc2 (which still carries libgcc as part of libroot.so). * Drop filtering of libgcc objects for libroot, as that is no longer necessary since we're only using libgcc-as-single-object for libroot with x86_gcc2, where the filtered object file doesn't exist. Should the objects that used to be filtered cause any problems as part of libgcc_s.so, we can always filter them as part of the gcc build. * Use libsupc++.so from the gcc_syslibs build feature for everything but x86_gcc2. * Adjust all Jamfiles accordingly. * Deactivate building of faked libstdc++.so for non-x86-gcc2. For x86_gcc2, we still build libstdc++.so from the sources in the Haiku source tree as part of the Haiku build . * Put gcc_syslibs package onto the image, when needed.
|
#
1b744548e0a31d725a147cfeadf3eeb30a4eb84c |
|
15-Dec-2013 |
Rene Gollent <rene@gollent.com> |
debug_server: Add default action support. - debug_server now supports user configuration of both the general default action to be taken on crashes, and per-app overrides. These are stored config/settings/system/debug_server/settings. In the absence of the file, behavior defaults to prompting the user for an action as before. The file takes on a driver_settings style format as follows: --- default_action user executable_actions { app1 log /path/app2* debug } --- Valid values for an action are: - user = prompt user for action. - kill = silently terminate the crashing team. - debug = attach the debugger to the crashing team. in the debugger. - log / report = save a crash report and terminate the team. If no default_action is specified, "user" is assumed. The executable_actions subsection contains individual overrides of the default. These take the form above, where the individual lines can be only a team name, or a path, with wildcards. Implements first part of #10301.
|
#
b0944c78b074a8110bd98e060415d0e8f38a7f65 |
|
01-Aug-2013 |
Ingo Weinhold <ingo_weinhold@gmx.de> |
More work towards hybrid support * All packaging architecture dependent variables do now have a respective suffix and are set up for each configured packaging architecture, save for the kernel and boot loader variables, which are still only set up for the primary architecture. For convenience TARGET_PACKAGING_ARCH, TARGET_ARCH, TARGET_LIBSUPC++, and TARGET_LIBSTDC++ are set to the respective values for the primary packaging architecture by default. * Introduce a set of MultiArch* rules to help with building targets for multiple packaging architectures. Generally the respective targets are (additionally) gristed with the packaging architecture. For libraries the additional grist is usually omitted for the primary architecture (e.g. libroot.so and <x86>libroot.so for x86_gcc2/x86 hybrid), so that Jamfiles for targets built only for the primary architecture don't need to be changed. * Add multi-arch build support for all targets needed for the stage 1 cross devel package as well as for libbe (untested).
|
#
8215661bb2811fb6166433a87fd09123e88ea2b3 |
|
29-Oct-2011 |
François Revol <revol@free.fr> |
Apply patch by 'mt' from ticket #7622 to localize the debug_server alert. Thanks! git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@42979 a95241bf-73f2-0310-859d-f6bbb57e9c96
|
#
338b8dc301721b1f472e8297a898d4eaa2f2ee3a |
|
29-Oct-2005 |
Ingo Weinhold <ingo_weinhold@gmx.de> |
Merged changes from branch build_system_redesign at revision 14573. git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@14574 a95241bf-73f2-0310-859d-f6bbb57e9c96
|
#
c9ce15c94a19b9cb1b0a8c4e9f3fde589bc42cf6 |
|
14-Jul-2005 |
Ingo Weinhold <ingo_weinhold@gmx.de> |
* Reworked the design: It certainly doesn't make sense to display more than one alert, when two threads of a team crash. Now we have a per team queue of debug messages and a thread per team that processes them (that is usually only the first one). The application class does nothing anymore. * Implemented debugger handover: - In case of normal apps, when the relevant servers needed for GUI are running, we show an alert and, if requested, start a MiniTerminal with gdb for the crashed team. I couldn't really test it, since alerts don't seem to work, respectively crash the app server (usually both ;-). - In case the app server crashes, we always start a consoled with gdb. This does indeed seem to work. A gdb attached to a team is not really useful yet, since the shared object relocations seem to be incorrect, so "bt" is not giving any useful info. git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@13684 a95241bf-73f2-0310-859d-f6bbb57e9c96
|
#
362e09b1247897f6d6956b6a6dfc0759b8b45d5a |
|
20-Mar-2005 |
Ingo Weinhold <ingo_weinhold@gmx.de> |
In case of a debugger() call now also prints the debug message. Makes use of the new libdebug.so. git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@11926 a95241bf-73f2-0310-859d-f6bbb57e9c96
|
#
35e49f2582eed6a36620f79de55d4c9f3bfe3a30 |
|
25-Feb-2005 |
Ingo Weinhold <ingo_weinhold@gmx.de> |
Initial version of our debug server. This is the guy that hangs around waiting for teams to crash to show our favorite alert. Due to the missing app_server we don't show a alert yet. We just print something to /dev/dprintf and kill the team. Unlike R5's debug server ours will probably not provide any debugging functionality itself, but rather employ gdb directly. git-svn-id: file:///srv/svn/repos/haiku/trunk/current@11492 a95241bf-73f2-0310-859d-f6bbb57e9c96
|