When developers modify a software program to add features, or refactor existing code, they may inadvertently introduce a bug, resulting in a broken version. In such situations called differential debugging scenario, developers need to under- stand why two versions behave differently to solve the bug. To assess the perceived impact of differential debugging scenario, we conducted a preliminary study through a sur- vey of 212 developers from diverse professional backgrounds and domains. The results show that differential debugging scenarios are widespread: 93% of respondents reported hav- ing encountered this type of bug at least once. Moreover, more than half of the participants indicated that these sce- narios have an impact on their development activities, often requiring time and effort to resolve. Our findings also highlight mixed perceptions regarding the adequacy of existing practices and tools. While preven- tive techniques such as continuous integration and code review are generally viewed as helpful, many developers report that current debugging tools provide limited support for understanding the causes of failures introduced between versions. Overall, this survey provides an initial, large-scale characterization of how developers perceive differential de- bugging scenarios and motivates further empirical research on how such bugs are handled in practice and how tool support could be improved.